[
https://issues.apache.org/jira/browse/SOLR-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-8085:
-------------------------------
Attachment: fail.150922_125320
Here's a fail from HdfsChaosMonkeySafeLeaderTest on trunk (with some minor
patches provided by Mark).
Throwable #1: java.lang.AssertionError: shard3 is not consistent. Got 658 from
http://127.0.0.1:44649/collection1lastClient and got 330 from
http://127.0.0.1:38249/collection1
> 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: fail.150922_125320
>
>
> 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]
