[
https://issues.apache.org/jira/browse/SOLR-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903479#comment-14903479
]
Mark Miller commented on SOLR-8085:
-----------------------------------
bq. I'm trying a possible solution now where we won't allow peer sync after a
recovery that is not successful.
This seems to work out well.
Most of these issues show up easier when running the more heavyweight hdfs
tests though, so I am running those - because we truncate support in hdfs was
not added until 2.7, when a replication fails, we still replay all the buffered
docs. A badly timed server restart can then pass incorrectly on peer sync if
this happens, regardless of my attempted fix that won't cross jetty restarts.
> 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, 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]
