Aha, you are right wrdrvf! The query is forwarded to any of the active
shards (I saw the query alternate between both of mine). Nice feature.
Also, looking at 'ClusterStateAwarePingRequestHandler' (which I downloaded
from www.manning.com/SolrinAction), it is checking zookeeper to see if the
logical
Try querying the recovering core with distrib=false, you should get the count
of docs in it.
Most likely, since the replica is recovering it is forwarding all queries to
the active replica, this can be verified in the core logs.
--
View this message in context:
http://lucene.472066.n3.nabble
No, we're not doing NRT. The search clients aren't using CloudSolrServer
and they are behind an AWS load balancer, which calls the Solr ping handler
(implemented with ClusterStateAwarePingRequestHandler) to determine when
the node is active. This ping handler also responds during the index copy,
wh
I don’t know offhand about the num docs issue - are you doing NRT?
As far as being able to query the replica, I’m not sure anyone ever got to
making that fail if you directly query a node that is not active. It certainly
came up, but I have no memory of anyone tackling it. Of course in many othe
