I've had similar problems. Two things that helped:
1. If index had more than one shard then optimizing it to one shard usually
worked.
2. In other case manually copying shard files from node with master shard
to one of nodes that kept failing.
On Sunday, 30 November 2014 00:57:02 UTC+1, David
Small mistake. 1. should be:
1. If shard had more than one segment then optimizing it to one segment
usually worked.
On Sunday, 30 November 2014 12:00:37 UTC+1, Jakub Podeszwik wrote:
I've had similar problems. Two things that helped:
1. If index had more than one shard then optimizing it to
Hey David, I have same problem now. Have you found a solution for that
problem?
26 Ağustos 2014 Salı 23:08:55 UTC+3 tarihinde David Kleiner yazdı:
Hello,
In the past couple of days I've been getting a lot of error messages about
corrupted replica shards. The primary shards come up fast
Hello Mehmet,
For two indices with problematic shards (symptoms: shard is recovering,
recovery stops and recovery is attempted on a different node), I manually
changed replica count to 1 then 2. With a big index (over 90G, I think), I
was never able to recover dual replica set, thankfully it
Hello,
In the past couple of days I've been getting a lot of error messages about
corrupted replica shards. The primary shards come up fast after ES process
restart but replicas take a long time to come back. Sometimes it takes a
few node restarts to 'kick' the nodes to start replica shards.
