OpenSearch/docs/reference/index-modules/allocation/prioritization.asciidoc

57 lines
1.4 KiB
Plaintext
Raw Normal View History

2015-07-15 12:05:42 -04:00
[[recovery-prioritization]]
=== Index recovery prioritization
Unallocated shards are recovered in order of priority, whenever possible.
Indices are sorted into priority order as follows:
* the optional `index.priority` setting (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
2015-07-15 12:05:42 -04:00
the index prioritization order. For instance:
[source,js]
2015-07-15 12:05:42 -04:00
------------------------------
PUT index_1
PUT index_2
Update the default for include_type_name to false. (#37285) * Default include_type_name to false for get and put mappings. * Default include_type_name to false for get field mappings. * Add a constant for the default include_type_name value. * Default include_type_name to false for get and put index templates. * Default include_type_name to false for create index. * Update create index calls in REST documentation to use include_type_name=true. * Some minor clean-ups around the get index API. * In REST tests, use include_type_name=true by default for index creation. * Make sure to use 'expression == false'. * Clarify the different IndexTemplateMetaData toXContent methods. * Fix FullClusterRestartIT#testSnapshotRestore. * Fix the ml_anomalies_default_mappings test. * Fix GetFieldMappingsResponseTests and GetIndexTemplateResponseTests. We make sure to specify include_type_name=true during xContent parsing, so we continue to test the legacy typed responses. XContent generation for the typeless responses is currently only covered by REST tests, but we will be adding unit test coverage for these as we implement each typeless API in the Java HLRC. This commit also refactors GetMappingsResponse to follow the same appraoch as the other mappings-related responses, where we read include_type_name out of the xContent params, instead of creating a second toXContent method. This gives better consistency in the response parsing code. * Fix more REST tests. * Improve some wording in the create index documentation. * Add a note about types removal in the create index docs. * Fix SmokeTestMonitoringWithSecurityIT#testHTTPExporterWithSSL. * Make sure to mention include_type_name in the REST docs for affected APIs. * Make sure to use 'expression == false' in FullClusterRestartIT. * Mention include_type_name in the REST templates docs.
2019-01-14 16:08:01 -05:00
PUT index_3?include_type_name=true
2015-07-15 12:05:42 -04:00
{
"settings": {
"index.priority": 10
}
}
Update the default for include_type_name to false. (#37285) * Default include_type_name to false for get and put mappings. * Default include_type_name to false for get field mappings. * Add a constant for the default include_type_name value. * Default include_type_name to false for get and put index templates. * Default include_type_name to false for create index. * Update create index calls in REST documentation to use include_type_name=true. * Some minor clean-ups around the get index API. * In REST tests, use include_type_name=true by default for index creation. * Make sure to use 'expression == false'. * Clarify the different IndexTemplateMetaData toXContent methods. * Fix FullClusterRestartIT#testSnapshotRestore. * Fix the ml_anomalies_default_mappings test. * Fix GetFieldMappingsResponseTests and GetIndexTemplateResponseTests. We make sure to specify include_type_name=true during xContent parsing, so we continue to test the legacy typed responses. XContent generation for the typeless responses is currently only covered by REST tests, but we will be adding unit test coverage for these as we implement each typeless API in the Java HLRC. This commit also refactors GetMappingsResponse to follow the same appraoch as the other mappings-related responses, where we read include_type_name out of the xContent params, instead of creating a second toXContent method. This gives better consistency in the response parsing code. * Fix more REST tests. * Improve some wording in the create index documentation. * Add a note about types removal in the create index docs. * Fix SmokeTestMonitoringWithSecurityIT#testHTTPExporterWithSSL. * Make sure to mention include_type_name in the REST docs for affected APIs. * Make sure to use 'expression == false' in FullClusterRestartIT. * Mention include_type_name in the REST templates docs.
2019-01-14 16:08:01 -05:00
PUT index_4?include_type_name=true
2015-07-15 12:05:42 -04:00
{
"settings": {
"index.priority": 5
}
}
------------------------------
// CONSOLE
2015-07-15 12:05:42 -04:00
In the above example:
* `index_3` will be recovered first because it has the highest `index.priority`.
* `index_4` will be recovered next because it has the next highest priority.
* `index_2` will be recovered next because it was created more recently.
* `index_1` will be recovered last.
This setting accepts an integer, and can be updated on a live index with the
<<indices-update-settings,update index settings API>>:
[source,js]
2015-07-15 12:05:42 -04:00
------------------------------
PUT index_4/_settings
{
"index.priority": 1
}
------------------------------
// CONSOLE
// TEST[continued]