elasticsearch/elasticsearch — Issue #1717: Failed shards allocation can "poison" allocation and might cause not allocating other shards
Author: kimchy
Created: 2012-02-17 22:11:34+00:00
State: open
Labels: enhancement, v0.19.0.RC3

Its pretty rare, but might happen, specifically when having many indices (and many shards) and if some shards fail, it might end in a poison state where failed shards are retried and because of shards concurrent initialization limits per node, the same might be attempted to start each time.

Obviously, it would be great to have something that identified that a specific shard has failed on all its different replicas, and then throttle its attempted allocation to a later time, but thats a different issue.