> 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 wi
Solr is provides availability and it is tolerant to partioning so that leaves
consistency. It is eventual consistent.
-Original message-
> From:Bill Au
> Sent: Fri 16-Nov-2012 15:00
> To: solr-user@lucene.apache.org
> Subject: Re: consistency in SolrCloud replication
27;re saying the commit call will not return unless all
> > > replicas have completed their commits. Right?
> > >
> > > ~ David
> > >
> > >
> > >
> > > -
> > > Author:
> > http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
> > > --
> > > View this message in context:
> >
> http://lucene.472066.n3.nabble.com/consistency-in-SolrCloud-replication-tp4020379p4020518.html
> > > Sent from the Solr - User mailing list archive at Nabble.com.
> >
> >
>
; > commit. So you're saying the commit call will not return unless all
> > replicas have completed their commits. Right?
> >
> > ~ David
> >
> >
> >
> > -
> > Author:
> http://www.packtpub.com/apache-solr-3-enterprise-search-server/
: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/consistency-in-SolrCloud-replication-tp4020379p4020518.html
> Sent from the Solr - User mailing list archive at Nabble.com.
he commit call will not return unless all
replicas have completed their commits. Right?
~ David
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context:
http://lucene.472066.n3.nabble.com/consistency-in-SolrCloud-replication-tp402037
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 "mo
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 wrote:
> It's included as soon as it has been indexed - though a request won't
> return until it's a
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 wrote:
> Will a newly indexed document included in search result in the shard leader
> as soon as it has
