Is this documented anywhere outside of the JIRAs you mentioned Erick
(or anyone else)? I can only speak for myself, but I don't think I
would've expected/caught that as a potential Solr consumer, even
though it is working as designed. If it doesn't make sense to
actually this; ensuring this is
If I kill a replica with -9, the state.json node never gets updated,
the node shows as "active"
There is code around that checks the live_nodes to see whether the
state.json node can be believed, and Varun pointed me at Solr JIRAs
for making sure CLUSTERSTATUS consults live_nodes, indicating that
This is expected and works as designed. We have enough complexity in
publishing state for other nodes (LIR) and we shouldn't add any more.
Besides what if the leader itself was killed, who changes the state
then?
What problem are you trying to solve?
On Fri, Oct 23, 2015 at 10:19 PM, Erick
Not so much a problem as behavior I wasn't fully expecting. It does
seem a little trappy to have this thing that's supposed to be the
state of the collection but then require that another znode be
checked to see if state.json is telling the truth.
In the particular case that came up, a monitoring
