Index recovery prioritizationedit
Unallocated shards are recovered in order of priority, whenever possible. Indices are sorted into priority order as follows:
-
the optional
index.prioritysetting (higher before lower) - the index creation date (higher before lower)
- the index name (higher before lower)
This means that, by default, newer indices will be recovered before older indices.
Use the per-index dynamically updatable index.priority setting to customise
the index prioritization order. For instance:
response = client.indices.create(
index: 'index_1'
)
puts response
response = client.indices.create(
index: 'index_2'
)
puts response
response = client.indices.create(
index: 'index_3',
body: {
settings: {
'index.priority' => 10
}
}
)
puts response
response = client.indices.create(
index: 'index_4',
body: {
settings: {
'index.priority' => 5
}
}
)
puts response
PUT index_1
PUT index_2
PUT index_3
{
"settings": {
"index.priority": 10
}
}
PUT index_4
{
"settings": {
"index.priority": 5
}
}
In the above example:
-
index_3will be recovered first because it has the highestindex.priority. -
index_4will be recovered next because it has the next highest priority. -
index_2will be recovered next because it was created more recently. -
index_1will be recovered last.
This setting accepts an integer, and can be updated on a live index with the update index settings API:
response = client.indices.put_settings(
index: 'index_4',
body: {
'index.priority' => 1
}
)
puts response
PUT index_4/_settings
{
"index.priority": 1
}