[ https://issues.apache.org/jira/browse/SOLR-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340556#comment-14340556 ]
ASF subversion and git services commented on SOLR-7033: ------------------------------------------------------- Commit 1662784 from [~steve_rowe] in branch 'dev/branches/lucene_solr_4_10' [ https://svn.apache.org/r1662784 ] SOLR-7033, SOLR-5961: RecoveryStrategy should not publish any state when closed / cancelled and there should always be a pause between recoveries even when recoveries are rapidly stopped and started as well as when a node attempts to become the leader for a shard. (merged branch_5x r1658237) > RecoveryStrategy should not publish any state when closed / cancelled. > ---------------------------------------------------------------------- > > Key: SOLR-7033 > URL: https://issues.apache.org/jira/browse/SOLR-7033 > Project: Solr > Issue Type: Bug > Reporter: Mark Miller > Assignee: Steve Rowe > Priority: Blocker > Fix For: 4.10.4, 5.0, Trunk > > Attachments: SOLR-7033.patch, SOLR-7033.patch, SOLR-7033.patch, > SOLR-7033.patch, SOLR-7033.patch > > > Currently, when closed / cancelled, RecoveryStrategy can publish a recovery > failed state. In a bad loop (like when no one can become leader because no > one had a last state of active) this can cause very fast looped publishing of > this state to zk. > It's an outstanding item to improve that specific scenario anyway, but > regardless, we should fix the close / cancel path to never publish any state > to zk. -- 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