Given a 4 node Solr Cloud (i.e. 2 shards, 2 replicas per shard). Let's say one node becomes 'nonresponsive'. Meaning sockets get created, but transactions to them don't get handled (i.e. they time out). We'll also assume that means the solr instance can't send information out to zookeeper or other solar instances.
Does ZK become aware of the issue at all? Do normal indexing operations fail (I would assume so based on a timeout, but just checking)? What would happen with query requests (let's assume the requests aren't sent directly to the 'hung' instance). Do some queries succeed, but others fail (i.e. timeout) based upon whether the node in the shard asked to handle the query is the 'hung' one or not? Is there an automatic timeout functionality where all queries will still succeed, but some will be much slower(i.e. if the 'hung' one is asked to handle it, there'll be a timeout and then the other core on the shard will be asked to handle it)? Thanks, Garth
