[ https://issues.apache.org/jira/browse/SOLR-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383719#comment-14383719 ]
Ramkumar Aiyengar commented on SOLR-7134: ----------------------------------------- Mark, do you plan to merge this to branch_5x soon? I wanted to merge my commit for SOLR-7291, which I still can, but will end up causing a few conflicts for you when you merge -- hence wanted to check.. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org