-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Closed
Labels
Team:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//release_note:enhancement
Description
Kibana depends on the .kibana index being allocated. During an Elasticsearch outage, it would probably be a good idea to get .kibana allocated as fast as possible so that they can start using it as soon as possible.
As such, we should be start specifying the index.priority setting as a high integer value. By default, the value is 1 and the highest value will always be allocated first. By allocating ours first (or faster), we can allow the user to get back to work sooner especially because the .kibana index tends to be very small and therefore it is easy to allocate quickly unlike shards that may have many GBs of data.
PUT .kibana
{
"settings": {
"index.priority": 10000
}
}tylersmalley, Leaf-Lin, lystor and mshustov
Metadata
Metadata
Assignees
Labels
Team:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//release_note:enhancement