[
https://issues.apache.org/jira/browse/SOLR-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972633#comment-14972633
]
Yonik Seeley commented on SOLR-8129:
------------------------------------
bq. I'm still first trying to find out why one update was rejected and then
updates that happened after that were still processed though.
OK, figured it out... it was my incorrect mental model assuming that there was
a single ConcurrentUpdateSolrClient between a leader and a replica.
I made that leap looking at StreamingSolrClients.getSolrClient called from
SolrCmdDistributor. But there is a different SolrCmdDistributor created per
update request to Solr.
So there is no longer any mystery around the reject followed by many other
updates. Different client objects (and once they have runners going, they can
keep going processing updates).
> HdfsChaosMonkeyNothingIsSafeTest failures
> -----------------------------------------
>
> Key: SOLR-8129
> URL: https://issues.apache.org/jira/browse/SOLR-8129
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Attachments: fail.151005_064958, fail.151005_080319
>
>
> New HDFS chaos test in SOLR-8123 hits a number of types of failures,
> including shard inconsistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
