Skip to content

more tag cleanup again #4489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shainaraskas merged 2 commits into from
Jan 5, 2026
Merged

more tag cleanup again #4489

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5c868b0
more
shainaraskas Dec 31, 2025
afa4856
Merge branch 'main' into tag-cleanup-sr-4
shainaraskas Jan 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
255 changes: 16 additions & 239 deletions troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,6 @@
- https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-shards-capacity-issues.html
applies_to:
stack:
deployment:
eck:
ess:
ece:
self:
products:
- id: elasticsearch
---
Expand All @@ -21,34 +16,17 @@
{{es}} limits the maximum number of shards to be held per node using the [`cluster.max_shards_per_node`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node) and [`cluster.max_shards_per_node.frozen`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node-frozen) settings. The current shards capacity of the cluster is available in the [health API shards capacity section](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-health-report).


## Cluster is close to reaching the configured maximum number of shards for data nodes. [_cluster_is_close_to_reaching_the_configured_maximum_number_of_shards_for_data_nodes]
## Cluster is close to reaching the configured maximum number of shards for data nodes[_cluster_is_close_to_reaching_the_configured_maximum_number_of_shards_for_data_nodes]

The [`cluster.max_shards_per_node`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node) cluster setting limits the maximum number of open shards for a cluster, only counting data nodes that do not belong to the frozen tier.

This symptom indicates that action should be taken, otherwise, either the creation of new indices or upgrading the cluster could be blocked.

If you’re confident your changes won’t destabilize the cluster, you can temporarily increase the limit using the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings):
If you're confident your changes won't destabilize the cluster, you can temporarily increase the limit using the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings).

Check notice on line 25 in troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.FutureTense: 'won't destabilize' might be in future tense. Write in the present tense to describe the state of the product as it is now.

:::::::{tab-set}
You can perform the following steps using either [API console](/explore-analyze/query-filter/tools/console.md), or direct [{{es}} API](elasticsearch://reference/elasticsearch/rest-apis/index.md) calls.

::::::{tab-item} {{ech}}
**Use {{kib}}**

1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
2. On the **Hosted deployments** panel, click the name of your deployment.

::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
::::

3. Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to **Dev Tools > Console**.

:::{image} /troubleshoot/images/elasticsearch-reference-kibana-console.png
:alt: {{kib}} Console
:screenshot:
:::

4. Check the current status of the cluster according the shards capacity indicator:
1. Check the current status of the cluster according the shards capacity indicator:

```console
GET _health_report/shards_capacity
Expand Down Expand Up @@ -86,7 +64,7 @@
1. Current value of the setting `cluster.max_shards_per_node`
2. Current number of open shards across the cluster

5. Update the [`cluster.max_shards_per_node`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node) setting with a proper value:
2. Update the [`cluster.max_shards_per_node`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node) setting with a proper value using the [cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings):

```console
PUT _cluster/settings
Expand All @@ -97,9 +75,9 @@
}
```

This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or [reduce your cluster’s shard count](../../deploy-manage/production-guidance/optimize-performance/size-shards.md#reduce-cluster-shard-count) on nodes that do not belong to the frozen tier.
This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or [reduce your cluster's shard count](../../deploy-manage/production-guidance/optimize-performance/size-shards.md#reduce-cluster-shard-count) on nodes that do not belong to the frozen tier.

6. To verify that the change has fixed the issue, you can get the current status of the `shards_capacity` indicator by checking the `data` section of the [health API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-health-report):
3. To verify that the change has fixed the issue, check the current status of the `shards_capacity` indicator:

```console
GET _health_report/shards_capacity
Expand Down Expand Up @@ -127,7 +105,7 @@
}
```

7. When a long-term solution is in place, we recommend you reset the `cluster.max_shards_per_node` limit.
4. When a long-term solution is in place, reset the `cluster.max_shards_per_node` limit:

```console
PUT _cluster/settings
Expand All @@ -137,128 +115,18 @@
}
}
```
::::::

::::::{tab-item} Self-managed
Check the current status of the cluster according the shards capacity indicator:

```console
GET _health_report/shards_capacity
```

The response will look like this:

```console-result
{
"cluster_name": "...",
"indicators": {
"shards_capacity": {
"status": "yellow",
"symptom": "Cluster is close to reaching the configured maximum number of shards for data nodes.",
"details": {
"data": {
"max_shards_in_cluster": 1000, <1>
"current_used_shards": 988 <2>
},
"frozen": {
"max_shards_in_cluster": 3000
}
},
"impacts": [
...
],
"diagnosis": [
...
}
}
}
```

1. Current value of the setting `cluster.max_shards_per_node`
2. Current number of open shards across the cluster


Using the [`cluster settings API`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings), update the [`cluster.max_shards_per_node`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node) setting:

```console
PUT _cluster/settings
{
"persistent" : {
"cluster.max_shards_per_node": 1200
}
}
```

This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or [reduce your cluster’s shard count](../../deploy-manage/production-guidance/optimize-performance/size-shards.md#reduce-cluster-shard-count) on nodes that do not belong to the frozen tier. To verify that the change has fixed the issue, you can get the current status of the `shards_capacity` indicator by checking the `data` section of the [health API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-health-report):

```console
GET _health_report/shards_capacity
```

The response will look like this:

```console-result
{
"cluster_name": "...",
"indicators": {
"shards_capacity": {
"status": "green",
"symptom": "The cluster has enough room to add new shards.",
"details": {
"data": {
"max_shards_in_cluster": 1200
},
"frozen": {
"max_shards_in_cluster": 3000
}
}
}
}
}
```

When a long-term solution is in place, we recommend you reset the `cluster.max_shards_per_node` limit.

```console
PUT _cluster/settings
{
"persistent" : {
"cluster.max_shards_per_node": null
}
}
```
::::::

:::::::

## Cluster is close to reaching the configured maximum number of shards for frozen nodes. [_cluster_is_close_to_reaching_the_configured_maximum_number_of_shards_for_frozen_nodes]
## Cluster is close to reaching the configured maximum number of shards for frozen nodes[_cluster_is_close_to_reaching_the_configured_maximum_number_of_shards_for_frozen_nodes]

The [`cluster.max_shards_per_node.frozen`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node-frozen) cluster setting limits the maximum number of open shards for a cluster, only counting data nodes that belong to the frozen tier.

This symptom indicates that action should be taken, otherwise, either the creation of new indices or upgrading the cluster could be blocked.

If you’re confident your changes won’t destabilize the cluster, you can temporarily increase the limit using the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings):

:::::::{tab-set}

::::::{tab-item} {{ech}}
**Use {{kib}}**

1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
2. On the **Hosted deployments** panel, click the name of your deployment.

::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
::::

3. Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to **Dev Tools > Console**.
If you're confident your changes won't destabilize the cluster, you can temporarily increase the limit using the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings).

Check notice on line 125 in troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.FutureTense: 'won't destabilize' might be in future tense. Write in the present tense to describe the state of the product as it is now.

:::{image} /troubleshoot/images/kibana-console.png
:alt: {{kib}} Console
:screenshot:
:::
You can perform the following steps using either [API console](/explore-analyze/query-filter/tools/console.md), or direct [{{es}} API](elasticsearch://reference/elasticsearch/rest-apis/index.md) calls.

4. Check the current status of the cluster according the shards capacity indicator:
1. Check the current status of the cluster according the shards capacity indicator:

```console
GET _health_report/shards_capacity
Expand Down Expand Up @@ -295,7 +163,7 @@
1. Current value of the setting `cluster.max_shards_per_node.frozen`
2. Current number of open shards used by frozen nodes across the cluster

5. Update the [`cluster.max_shards_per_node.frozen`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node-frozen) setting:
2. Update the [`cluster.max_shards_per_node.frozen`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node-frozen) setting using the [cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings):

```console
PUT _cluster/settings
Expand All @@ -306,9 +174,9 @@
}
```

This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or [reduce your cluster’s shard count](../../deploy-manage/production-guidance/optimize-performance/size-shards.md#reduce-cluster-shard-count) on nodes that belong to the frozen tier.
This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or [reduce your cluster's shard count](../../deploy-manage/production-guidance/optimize-performance/size-shards.md#reduce-cluster-shard-count) on nodes that belong to the frozen tier.

6. To verify that the change has fixed the issue, you can get the current status of the `shards_capacity` indicator by checking the `data` section of the [health API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-health-report):
3. To verify that the change has fixed the issue, check the current status of the `shards_capacity` indicator:

```console
GET _health_report/shards_capacity
Expand Down Expand Up @@ -336,7 +204,7 @@
}
```

7. When a long-term solution is in place, we recommend you reset the `cluster.max_shards_per_node.frozen` limit.
4. When a long-term solution is in place, reset the `cluster.max_shards_per_node.frozen` limit:

```console
PUT _cluster/settings
Expand All @@ -346,94 +214,3 @@
}
}
```
::::::

::::::{tab-item} Self-managed
Check the current status of the cluster according the shards capacity indicator:

```console
GET _health_report/shards_capacity
```

```console-result
{
"cluster_name": "...",
"indicators": {
"shards_capacity": {
"status": "yellow",
"symptom": "Cluster is close to reaching the configured maximum number of shards for frozen nodes.",
"details": {
"data": {
"max_shards_in_cluster": 1000
},
"frozen": {
"max_shards_in_cluster": 3000, <1>
"current_used_shards": 2998 <2>
}
},
"impacts": [
...
],
"diagnosis": [
...
}
}
}
```

1. Current value of the setting `cluster.max_shards_per_node.frozen`.
2. Current number of open shards used by frozen nodes across the cluster.


Using the [`cluster settings API`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings), update the [`cluster.max_shards_per_node.frozen`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node-frozen) setting:

```console
PUT _cluster/settings
{
"persistent" : {
"cluster.max_shards_per_node.frozen": 3200
}
}
```

This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or [reduce your cluster’s shard count](../../deploy-manage/production-guidance/optimize-performance/size-shards.md#reduce-cluster-shard-count) on nodes that belong to the frozen tier. To verify that the change has fixed the issue, you can get the current status of the `shards_capacity` indicator by checking the `data` section of the [health API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-health-report):

```console
GET _health_report/shards_capacity
```

The response will look like this:

```console-result
{
"cluster_name": "...",
"indicators": {
"shards_capacity": {
"status": "green",
"symptom": "The cluster has enough room to add new shards.",
"details": {
"data": {
"max_shards_in_cluster": 1000
},
"frozen": {
"max_shards_in_cluster": 3200
}
}
}
}
}
```

When a long-term solution is in place, we recommend you reset the `cluster.max_shards_per_node.frozen` limit.

```console
PUT _cluster/settings
{
"persistent" : {
"cluster.max_shards_per_node.frozen": null
}
}
```
::::::

:::::::
Loading