ou 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.c
.nabble.com/Question-about-solrcloud-recovery-process-tp4145450p4145491.html
Sent from the Solr - User mailing list archive at Nabble.com.
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
I bring up a new Solr node with no index and watch the index being
replicated from the leader. The index size is 12G and the replication takes
about 6 minutes, according to the replica log (from 'Starting recovery
process' to 'Finished recovery process). However, shortly after the
replication begin
