Hi James,
This might not be 100% what you are looking for but some ideas to
explore:
1. Change session timeout on ZooKeeper client; this might help you move
unresponsive node to "down" state and Solr Cloud will take affected node
out of rotation on its own.
Hi,
It is interesting that node reports healthy despite store access issue.
That node should be marked down if it can't open the core backing up
sharded collection.
Maybe if you could share exceptions/errors that you see in console/logs.
I have experienced issues with replica node not
Hello folks,
To start, we have a sharded solr cloud configuration running solr version 5.1.0
. During shard to shard communication there is a problem state where queries
are sent to a replica, and on that replica the storage is inaccessible. The
node is healthy so it’s still taking requests
