HealthCheck not working when network problems between the client and a Solr node

Hello, We are using Solr 8.5.2 We are having trouble with dealing with network errors between a Solr node and a client. In our situation, our Solr Nodes and Zk hosts are healthy and can communication with each other, all our collections are up and healthy. When we simulate a network proble

Re: colStatus response not as expected with Solr 8.1.1 in a distributed deployment

active unless its state is “active” in the state.json file _and_ the node appears in live_nodes. CLUSTERSTATUS pretty clearly understands this, but COLSTATUS apparently doesn’t. I’ll raise a JIRA. Thanks for letting us know Erick > On Oct 29, 2019, at 2:10 PM, Elizaveta Golova wrote: > > colS

Re: [EXTERNAL] Re: colStatus response not as expected with Solr 8.1.1 in a distributed deployment

Uhm, what is colStatus? You need to show us _exactly_ what Solr commands you’re running for us to make any intelligent comments. > On Oct 29, 2019, at 1:12 PM, Elizaveta Golova wrote: > > Hi, > > We're seeing an issue with colStatus in a distributed Solr deployment. > &g

colStatus response not as expected with Solr 8.1.1 in a distributed deployment

Hi, We're seeing an issue with colStatus in a distributed Solr deployment. Scenario: Collection with: - 1 zk - 2 solr nodes on different boxes (simulated using Docker containers) - replication factor 5 When we take down one node, our clusterStatus response is as expected (only listing the live