Yes, I *think* that is the case. Some distributed systems have the option to return success to caller only after data has been added/indexed to N other nodes, but I think Solr doesn't have this yet. Somebody please correct me if I'm wrong.
See: http://search-lucene.com/?q=eventually+consistent&fc_project=Solr Otis -- Solr & ElasticSearch Support http://sematext.com/ On Thu, Apr 11, 2013 at 12:51 PM, Zhang, Lisheng <lisheng.zh...@broadvision.com> wrote: > Hi Otis, > > Thanks very much for the quick help! We are considering to upgrade > from solr 3.6 to 4x and use solrCloud, but we are concerned about > performance related to replica? In this scenario it seems that the > replica would be a few seconds beyond leader because replica would > start indexing only afer leader finishes his? > > Thanks and best regards, Lisheng > > -----Original Message----- > From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com] > Sent: Thursday, April 11, 2013 8:11 AM > To: solr-user@lucene.apache.org > Subject: Re: SolrCloud leader to replica > > > I believe it indexes locally on leader first. Otherwise one could end > up with a situation where indexing to replica(s) succeeds and indexing > to leader fails, which I suspect might create a mess. > > Otis > -- > Solr & ElasticSearch Support > http://sematext.com/ > > > > > > On Thu, Apr 11, 2013 at 2:53 AM, Zhang, Lisheng > <lisheng.zh...@broadvision.com> wrote: >> Hi, >> >> In solr 4x solrCloud, suppose we have only one shard and >> two replica, when leader receives the indexing request, >> does it immediately forward request to two replicas or >> it first indexes request itself, then sends request to its >> two replica? >> >> Thanks very much for helps, Lisheng >> >>
