IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Total number of shards for an index on a single node exceeded Troubleshooting corruption »

› ›

Total number of shards per node has been reached

edit

Total number of shards per node has been reached

edit

Elasticsearch tries to take advantage of all the available resources by distributing data (index shards) amongst the cluster nodes.

Users might want to influence this data distribution by configuring the cluster.routing.allocation.total_shards_per_node system setting to restrict the number of shards that can be hosted on a single node in the system, regardless of the index. Various configurations limiting how many shards can be hosted on a single node can lead to shards being unassigned due to the cluster not having enough nodes to satisfy the configuration.

In order to fix this follow the next steps:

In order to get the shards assigned we’ll need to increase the number of shards that can be collocated on a node in the cluster. We’ll achieve this by inspecting the system-wide cluster.routing.allocation.total_shards_per_node cluster setting and increasing the configured value.

Use Kibana

Log in to the Elastic Cloud console.
On the Elasticsearch Service panel, click the name of your deployment.

If the name of your deployment is disabled your Kibana instances might be unhealthy, in which case please contact Elastic Support. If your deployment doesn’t include Kibana, all you need to do is enable it first.
Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to Dev Tools > Console.

Inspect the cluster.routing.allocation.total_shards_per_node cluster setting:

response = client.cluster.get_settings(
  flat_settings: true
)
puts response

GET /_cluster/settings?flat_settings

The response will look like this:

{
  "persistent": {
    "cluster.routing.allocation.total_shards_per_node": "300" 
  },
  "transient": {}
}

Represents the current configured value for the total number of shards that can reside on one node in the system.

Increase the value for the total number of shards that can be assigned on one node to a higher value:

response = client.cluster.put_settings(
  body: {
    persistent: {
      'cluster.routing.allocation.total_shards_per_node' => 400
    }
  }
)
puts response

PUT _cluster/settings
{
  "persistent" : {
    "cluster.routing.allocation.total_shards_per_node" : 400 
  }
}

The new value for the system-wide total_shards_per_node configuration is increased from the previous value of 300 to 400. The total_shards_per_node configuration can also be set to null, which represents no upper bound with regards to how many shards can be collocated on one node in the system.

In order to get the shards assigned you can add more nodes to your Elasticsearch cluster and assign the index’s target tier node role to the new nodes.

To inspect which tier is an index targeting for assignment, use the get index setting API to retrieve the configured value for the index.routing.allocation.include._tier_preference setting:

response = client.indices.get_settings(
  index: 'my-index-000001',
  name: 'index.routing.allocation.include._tier_preference',
  flat_settings: true
)
puts response

GET /my-index-000001/_settings/index.routing.allocation.include._tier_preference?flat_settings

The response will look like this:

{
  "my-index-000001": {
    "settings": {
      "index.routing.allocation.include._tier_preference": "data_warm,data_hot" 
    }
  }
}

Represents a comma separated list of data tier node roles this index is allowed to be allocated on, the first one in the list being the one with the higher priority i.e. the tier the index is targeting. e.g. in this example the tier preference is data_warm,data_hot so the index is targeting the warm tier and more nodes with the data_warm role are needed in the Elasticsearch cluster.

Alternatively, if adding more nodes to the Elasticsearch cluster is not desired, inspecting the system-wide cluster.routing.allocation.total_shards_per_node cluster setting and increasing the configured value:

Inspect the cluster.routing.allocation.total_shards_per_node cluster setting for the index with unassigned shards:
```
response = client.cluster.get_settings(
  flat_settings: true
)
puts response
```
```
GET /_cluster/settings?flat_settings
```
The response will look like this:
```
{
  "persistent": {
    "cluster.routing.allocation.total_shards_per_node": "300" 
  },
  "transient": {}
}
```
Represents the current configured value for the total number of shards that can reside on one node in the system.

Increase the value for the total number of shards that can be assigned on one node to a higher value:

response = client.cluster.put_settings(
  body: {
    persistent: {
      'cluster.routing.allocation.total_shards_per_node' => 400
    }
  }
)
puts response

PUT _cluster/settings
{
  "persistent" : {
    "cluster.routing.allocation.total_shards_per_node" : 400 
  }
}

« Total number of shards for an index on a single node exceeded Troubleshooting corruption »