On 5/12/2016 10:46 AM, Lars Noschinski wrote: > 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.
Each shard replica may have different information in the Solr caches, because they handled different queries. If you have cache autowarming enabled, it may take a substantially different amount of time to warm the caches, so the commit may take very different amounts of time on each replica. The changes may become visible on one replica sooner than they become visible on another replica, which means that you might have different requests return different information if executed before the commit as a whole completes. I would hope that if waitSearcher=true on the commit (which is the default setting), that the client would not receive a response until the entire collection across the cloud had processed the commit, but I do not know if that is in fact how it works. Thanks, Shawn
