[
https://issues.apache.org/jira/browse/SOLR-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8085:
------------------------------
Attachment: SOLR-8085.patch
Here is a patch I just ported to trunk that starts buffering before peer sync
and before we publish as RECOVERING.
With [[email protected]]'s fix and the couple I have, I've been able to hit
200 HdfsChaosMonkey test runs without replica inconsistency on my 4.10.3 +
backports based code for the first time.
> ChaosMonkey Safe Leader Test fail with shard inconsistency.
> -----------------------------------------------------------
>
> Key: SOLR-8085
> URL: https://issues.apache.org/jira/browse/SOLR-8085
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Attachments: SOLR-8085.patch, SOLR-8085.patch, fail.150922_125320,
> fail.150922_130608
>
>
> I've been discussing this fail I found with Yonik.
> The problem seems to be that a replica tries to recover and publishes
> recovering - the attempt then fails, but docs are now coming in from the
> leader. The replica tries to recover again and has gotten enough docs to pass
> peery sync.
> I'm trying a possible solution now where we won't allow peer sync after a
> recovery that is not successful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
