[SOLR-7134] Replication can still cause index corruption.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 5.1, 6.0
• Component/s: replication (java)
• Assignee: Mark Miller Assign to me
• Reporter: Mark Miller
• Created: 21/Feb/15 02:25
• Updated: 09/May/16 18:47
• Resolved: 27/Mar/15 20:19

Description

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.

Issue Links

• breaks: SOLR-9036 Solr slave is doing full replication (entire index) of index after master restart
• is related to: SOLR-8077 Replication can still cause index corruption.
• is related to: SOLR-7141 RecoveryStrategy: Raise time that we wait for any updates from the leader before they saw the recovery state to have finished.
• relates to: SOLR-6640 Replication can cause index corruption.
• relates to: SOLR-6920 During replication use checksums to verify if files are the same