You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A failed shard recovery (for example, because of OOM and the like) can cause shard data to be delete from disk. Though replicas can be there to recover from, it should not happen.
The text was updated successfully, but these errors were encountered:
We "lucked out" yesterday that enough of our nodes died with an out-of-heap error within a few minutes and we lost 3/4 of our shards (been furiously rebuilding on a new cluster since then).
a shard blows up (either out of memory, or in one case out of file descriptors).
Upon restarting the shard never recovers state with errors resembling (org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException) being thrown endlessly.
I wil be eagerly waiting for this patch to make it into the next stable release :)
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
A failed shard recovery (for example, because of OOM and the like) can cause shard data to be delete from disk. Though replicas can be there to recover from, it should not happen.
The text was updated successfully, but these errors were encountered: