[lucene-solr] branch SOLR-14581 created (now 55db208)

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

epugh pushed a change to branch SOLR-14581
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git.


      at 55db208  provide some detail on eventually consistent code

This branch includes the following new commits:

     new 55db208  provide some detail on eventually consistent code

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[lucene-solr] 01/01: provide some detail on eventually consistent code

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

epugh pushed a commit to branch SOLR-14581
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git

commit 55db208af9da2269d85f146a6e88c861c8bd5925
Author: epugh <ep...@opensourceconnections.com>
AuthorDate: Thu Jul 23 18:18:27 2020 -0400

    provide some detail on eventually consistent code
---
 solr/solr-ref-guide/src/shards-and-indexing-data-in-solrcloud.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/solr/solr-ref-guide/src/shards-and-indexing-data-in-solrcloud.adoc b/solr/solr-ref-guide/src/shards-and-indexing-data-in-solrcloud.adoc
index 3aa07cb..65d542b 100644
--- a/solr/solr-ref-guide/src/shards-and-indexing-data-in-solrcloud.adoc
+++ b/solr/solr-ref-guide/src/shards-and-indexing-data-in-solrcloud.adoc
@@ -122,6 +122,8 @@ More details on how to use shard splitting is in the section on the Collection A
 
 In most cases, when running in SolrCloud mode, indexing client applications should not send explicit commit requests. Rather, you should configure auto commits with `openSearcher=false` and auto soft-commits to make recent updates visible in search requests. This ensures that auto commits occur on a regular schedule in the cluster.
 
+NOTE: Using auto soft commit or commitWithin requires the client app to embrace the realities of "eventual consistency". Solr will make documents searchable at _roughly_ the same time across NRT replicas of a collection but there are no hard guarantees. Consequently, in rare cases, it's possible for a document to show up in one search only for it not to appear in a subsequent search occurring immediately after when the second search is routed to a different replica. Also, documents added [...]
+
 To enforce a policy where client applications should not send explicit commits, you should update all client applications that index data into SolrCloud. However, that is not always feasible, so Solr provides the `IgnoreCommitOptimizeUpdateProcessorFactory`, which allows you to ignore explicit commits and/or optimize requests from client applications without having refactor your client application code.
 
 To activate this request processor you'll need to add the following to your `solrconfig.xml`: