You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2015/02/21 03:26:11 UTC
[jira] [Created] (SOLR-7134) Replication can cause index
corruption.
Mark Miller created SOLR-7134:
---------------------------------
Summary: Replication can 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
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org