Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
9.0
-
None
-
None
Description
Distributed commit errors are not currently propagated back to the client that initially issued the commit command. So, any commit (e.g., issued via CloudSolrClient, curl to Http API, etc.) responds with Http status code 200, API status 0, as long as the commit to the "local" core arbitrarily associated with the request succeeds. This happens no matter how many distributed commits succeed or fail (at least, to other leader replicas – I've only tested w/ replication factor 1 at the moment).
Inconsistency – i.e. an error on an arbitrarily-determined "local" replica propagates propagates to the client, but an error on all other replicas does not – is the focus of this issue; but this issue is raised with no preconceived notions wrt how the inconsistency should be resolved.