Hi, On Fri, Apr 25, 2014 at 12:54 PM, zzT <zis....@gmail.com> wrote:
> Erick Erickson wrote > > 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. > > Hmm, I thought that it's not actual indexing taking place on the replicas > but that the changes were somehow transferred to the replicas and thus it > was less intensive for them. > Unfortunately that's not the case. Each node that gets a doc still has to analyze and index it. I think at some point I sent a message to the list and/or created a JIRA issue to suggest doing analysis on just the receiving node, in which case the other nodes that need to index could skip that step and do a little less work, but that hasn't been implemented yet. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ > > > Erick Erickson wrote > > 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. > > So, this is where SolrCloud is different from legacy master/slave > configuration? I mean master/slave sends segments to the slaves using e.g. > rsync while SolrCloud forwards the indexing request to replicas where it's > processed "locally" on each replica, right? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-load-balancing-during-heavy-indexing-tp4133099p4133160.html > Sent from the Solr - User mailing list archive at Nabble.com. >
