Seeing some recent problems on master where shortly after a cluster reboot
and full recovery (all shards green, all nodes connected), on occasion a
shard or two will start being marked as recovery (rebalancing is disabled,
so it's not due to it being moved around). After a few minutes they
sometimes say they're initializing (an order of magnitude after the amount
of time it should take to transfer the shard given all the throttling
settings and network), but in the end they'll never come back up and just
remain in that state until I manually reroute the shard or restart the
We were seeing similar problems on a larger scale on 0.90.3 (multiple
shards never recovering, all of them replicas of the same primary). I
thought I saw something about that being fixed on github, but can't recall
the exact issue now. Any chance these are related? Is there something I can
do to debug what is going on while the shards say initializing/recovering?
Nothing is currently coming up in my logs.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.