Back up, you're misunderstanding the update process. A leader node distributes the update to every replica. So _all_ your nodes in a slice are indexing when _any_ of them index. So the idea of sending queries to just the replicas to avoid performance problems isn't relevant.
In order to support NRT and HA/DR, it's required that all the nodes be ready to take over, so the notion of the leader being the only node that actually indexed the documents then distributing only the indexed document to the other members of the slice isn't how it's done. You're right, if you have a heavy indexing load it'll take resources from your query rate and it's something to be cognizant of, but it's a cluster-wide issue, not just an issue with the leader. Best, Erick On Fri, Apr 25, 2014 at 3:32 AM, zzT <zis....@gmail.com> wrote: > Hi all, > > In SolrCloud all nodes are equal in the sense that they can perform indexing > as well as searching. > > Let's say a leader node is busy performing heavy-indexing, I wouldn't like > to also send search requests to that node. As far as I can tell from > CloudSolrServer source code, all it does when dealing with search requests > is to shuffle the live nodes (info retrieved from Zookeeper) and choose one > of them. Does it perform anything smarter than that, like excluding leader > because of heavy indexing? > > Basically, what I'm worried about is a scenario where heavy indexing on > leader node might affect search response times. Has anyone witnessed such a > case? > > Thanks > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-load-balancing-during-heavy-indexing-tp4133099.html > Sent from the Solr - User mailing list archive at Nabble.com.
