mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-29 09:54:06 -04:00
35e705877b
Today if a shard fails during initialization phase due to misconfiguration, broken disks, missing analyzers, not installed plugins etc. elasticsaerch keeps on trying to initialize or rather allocate that shard. Yet, in the worst case scenario this ends in an endless allocation loop. To prevent this loop and all it's sideeffects like spamming log files over and over again this commit adds an allocation decider that stops allocating a shard that failed more than N times in a row to allocate. The number or retries can be configured via `index.allocation.max_retry` and it's default is set to `5`. Once the setting is updated shards with less failures than the number set per index will be allowed to allocate again. Internally we maintain a counter on the UnassignedInfo that is reset to `0` once the shards has been started. Relates to #18417 |
||
|---|---|---|
| .. | ||
| allocation-explain.asciidoc | ||
| health.asciidoc | ||
| nodes-hot-threads.asciidoc | ||
| nodes-info.asciidoc | ||
| nodes-stats.asciidoc | ||
| pending.asciidoc | ||
| reroute.asciidoc | ||
| state.asciidoc | ||
| stats.asciidoc | ||
| tasks.asciidoc | ||
| update-settings.asciidoc | ||