[ https://issues.apache.org/jira/browse/SOLR-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941215#comment-14941215 ]
ASF subversion and git services commented on SOLR-8085: ------------------------------------------------------- Commit 1706424 from [~markrmil...@gmail.com] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1706424 ] SOLR-8085: Fix a variety of issues that can result in replicas getting out of sync. > Fix a variety of issues that can result in replicas getting out of sync. > ------------------------------------------------------------------------ > > Key: SOLR-8085 > URL: https://issues.apache.org/jira/browse/SOLR-8085 > Project: Solr > Issue Type: Bug > Reporter: Mark Miller > Assignee: Mark Miller > Priority: Critical > Fix For: Trunk, 5.4 > > Attachments: SOLR-8085.patch, SOLR-8085.patch, SOLR-8085.patch, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org