Shalin, Given the earlier response by Erick, wondering when this scenario occurs i.e. when the replica node recovers after a time period, wouldn’t it automatically recover all the missed updates by connecting to the leader? My understanding is the below from the responses so far (assuming replication factor of 2 for simplicity purposes):
1. Client tries an update request which is received by the shard leader 2. Leader once it updates on its own node, send the update to the unavailable replica node 3. Leader keeps trying to send the update to the replica node 4. After a while leader gives up and communicates to the client (not sure what kind of message will the client receive in this case?) 5. Replica node recovers and then realises that it needs to catch-up and hence receives all the updates in recovery mode Correct me if I am wrong in my understanding. Thnx!! On 3 May 2018 at 04:10:12, Shalin Shekhar Mangar (shalinman...@gmail.com) wrote: The min_rf parameter does not fail indexing. It only tells you how many replicas received the live update. So if the value is less than what you wanted then it is up to you to retry the update later. On Wed, May 2, 2018 at 3:33 PM, Greenhorn Techie <greenhorntec...@gmail.com> wrote: > Hi, > > Good Morning!! > > In the case of a SolrCloud setup with sharing and replication in place, > when a document is sent for indexing, what happens when only the shard > leader has indexed the document, but the replicas failed, for whatever > reason. Will the document be resent by the leader to the replica shards to > index the document after sometime or how is scenario addressed? > > Also, given the above context, when I set the value of min_rf parameter to > say 2, does that mean the calling application will be informed that the > indexing failed? > -- Regards, Shalin Shekhar Mangar.
