[
https://issues.apache.org/jira/browse/SOLR-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett closed SOLR-9357.
-----------------------------------
Resolution: Duplicate
Some sort of accidental double-create it looks like, since SOLR-9355 has
verbatim the same description.
> ConcurrentUpdateSolrClient does not retry sending docs to followers
> -------------------------------------------------------------------
>
> Key: SOLR-9357
> URL: https://issues.apache.org/jira/browse/SOLR-9357
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 5.3, 6.x
> Reporter: Erick Erickson
>
> I'm a little out of my comfort zone, so posting this for discussion. If, for
> any reason, ConcurrentUpdateSolrClient doesn't get a response from a replica
> (say a network glitch or the like), it _seems_ to initiate a LIR on the
> replica. This is around line 243 in 5.3.2, and the corresponding code in 6x
> looks unchanged on a quick perusal.
> This is fragile in the sense that a simple retry could avoid the replica
> going into recovery if the problem is transient.
> I don't think this is issuing a retry higher in the stack, but we're seeing
> this behavior in the field so I'm posting this here for discussion, I've had
> a back-channel discussion already so a JIRA seems in order.
> The other thing I'm not entirely sure of is whether retrying at this point in
> the process is something that will avoid versioning problems, although I
> believe the docs already have a version stamp so it should be OK.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
