Actually, after shutting down the trouble node and bringing it up again, we've got a primary on the trouble shard. Now the other nodes are refusing to be replicas, perhaps due to something around the write.lock as well since they are getting the same error. It seems to just be shuffling the forever failing "recovering" shard around attempting to get the replica going.
-- 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1ee84237-e3a9-435a-9c95-90d1161a1e28%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
