I'm not a dev, but I would assume the following if I were concerned with
speed and atomicity
A. A commit WILL be reflected in all appropriate shards / replicas in a
very short time.
I believe Solr Cloud guarantees this, although the time frame
will be dependent on "B"
B. Network, processor, size, complexity of commit and indexing, and other
variables will have an affect on how fast it happens
C. It is possible that during the process of getting the data to all Solr
instances, a user could query at just the right moment and get "stale"
data, but that state will not last very long.
Others on this list may correct me... but that's my best understanding.
On Thu, May 12, 2016 at 10:46 AM, Lars Noschinski <lars.noschin...@qaware.de
> wrote:
> Hi everyone,
>
> does Solr (6.0) give an guarantees about the atomicity of commits in Solr
> Cloud? I.e., if I add a large amount of documents, then commit, do the
> changed state become visible on all shards at the same time? I could not
> find anything towards that, so I assume that there is no such guarantee.
>
> Best regards,
> Lars
> ------------------------------
> Lars Noschinski
> Softwareingenieur
>
> QAware GmbH
> Aschauer Str. 32
> 81549 München, Germany
> Tel +49 89 232315-213
> Fax +49 89 232315-129
> lars.noschin...@qaware.de
> www.qaware.de
> ------------------------------
> Geschäftsführer: Christian Kamm, Bernd Schlüter, Johannes Weigend, Dr.
> Josef Adersberger
> Registergericht: München
> Handelsregisternummer: HRB 163761
>
