Re: consistency in SolrCloud replication

2012-11-16 Thread Bill Au
Yes, my original question is about search. And Mark did answered is in his original reply. I am guessing that the replicas are updated sequentially so the newly added documents will be available in some replicas before other. I want to know where SolrCloud stands in terms of CAP. Bill On

RE: consistency in SolrCloud replication

2012-11-16 Thread Markus Jelsma
Solr is provides availability and it is tolerant to partioning so that leaves consistency. It is eventual consistent. -Original message- From:Bill Au bill.w...@gmail.com Sent: Fri 16-Nov-2012 15:00 To: solr-user@lucene.apache.org Subject: Re: consistency in SolrCloud replication

Re: consistency in SolrCloud replication

2012-11-16 Thread Mark Miller
I want to know where SolrCloud stands in terms of CAP. SolrCloud is a CP system. In the face of partitions, SolrCloud favors consistency over availability (mostly concerning writes). The system is eventually consistent, but should become consistent with a pretty low latency, unlike many cases

Re: consistency in SolrCloud replication

2012-11-15 Thread Bill Au
Thanks for the info, Mark. By a request won't return until it's affected all replicas, are you referring to the update request or the query? Bill On Wed, Nov 14, 2012 at 7:57 PM, Mark Miller markrmil...@gmail.com wrote: It's included as soon as it has been indexed - though a request won't

Re: consistency in SolrCloud replication

2012-11-15 Thread Mark Miller
I'm talking about an update request. So if you make an update, when it returns, your next search will see the update, because it will be on all replicas. Another process that is searching rapidly may see an eventually consistent view though (very briefly). We have some ideas to make that view more

Re: consistency in SolrCloud replication

2012-11-15 Thread David Smiley (@MITRE.org)
Mark Miller-3 wrote I'm talking about an update request. So if you make an update, when it returns, your next search will see the update, because it will be on all replicas. I presume this is only the case if (of course) the client also sent a commit. So you're saying the commit call will not

Re: consistency in SolrCloud replication

2012-11-15 Thread Mark Miller
It depends - no commit necessary for realtime get. Otherwise, yes, you would need to do at least a soft commit. That works the same way though - so if you make your update, then do a soft commit, you can be sure your next search will see the update on all the replicas. And with realtime get, of

Re: consistency in SolrCloud replication

2012-11-15 Thread Otis Gospodnetic
I think Bill was asking about search I think the Q is whether the query hitting the shard where a doc was sent for indexing would see that doc even before that doc has been copied to replicas. I didn't test it, but I'd think the answer would be positive because of the xa log. Otis --

Re: consistency in SolrCloud replication

2012-11-14 Thread Mark Miller
It's included as soon as it has been indexed - though a request won't return until it's affected all replicas. Low latency eventual consistency. - Mark On Nov 14, 2012, at 5:47 PM, Bill Au bill.w...@gmail.com wrote: Will a newly indexed document included in search result in the shard leader