[
https://issues.apache.org/jira/browse/SOLR-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338462#comment-14338462
]
Mark Miller commented on SOLR-7134:
-----------------------------------
A fair amount of flux since I've 'test beasted' this work - I'll spend some
time doing that with the latest patch this morning.
HdfsChaosMonkeySafeLeader test has been better at catching a lot of these
issues than ChaosMonkeySafeLeader test for some reason.
> Replication can still cause index corruption.
> ---------------------------------------------
>
> Key: SOLR-7134
> URL: https://issues.apache.org/jira/browse/SOLR-7134
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-7134.patch, SOLR-7134.patch, SOLR-7134.patch,
> SOLR-7134.patch, SOLR-7134.patch
>
>
> While we have plugged most of these holes, there appears to be another that
> is fairly rare.
> I've seen it play out a couple ways in tests, but it looks like part of the
> problem is that even if we decide we need a file and download it, we don't
> care if we then cannot move it into place if it already exists.
> I'm working with a fix that does two things:
> * Fail a replication attempt if we cannot move a file into place because it
> already exists.
> * If a replication attempt during recovery fails, on the next attempt force a
> full replication to a new directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
