[ https://issues.apache.org/jira/browse/SOLR-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738572#comment-14738572 ]
ASF subversion and git services commented on SOLR-7819: ------------------------------------------------------- Commit 1702213 from sha...@apache.org in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1702213 ] SOLR-7819: ZK connection loss or session timeout do not stall indexing threads anymore and LIR activity is moved to a background thread > ZkController.ensureReplicaInLeaderInitiatedRecovery does not respect > retryOnConnLoss > ------------------------------------------------------------------------------------ > > Key: SOLR-7819 > URL: https://issues.apache.org/jira/browse/SOLR-7819 > Project: Solr > Issue Type: Bug > Components: SolrCloud > Affects Versions: 5.2, 5.2.1 > Reporter: Shalin Shekhar Mangar > Labels: Jepsen > Fix For: Trunk, 5.4 > > Attachments: SOLR-7819.patch, SOLR-7819.patch, SOLR-7819.patch, > SOLR-7819.patch, SOLR-7819.patch, SOLR-7819.patch > > > SOLR-7245 added a retryOnConnLoss parameter to > ZkController.ensureReplicaInLeaderInitiatedRecovery so that indexing threads > do not hang during a partition on ZK operations. However, some of those > changes were unintentionally reverted by SOLR-7336 in 5.2. > I found this while running Jepsen tests on 5.2.1 where a hung update managed > to put a leader into a 'down' state (I'm still investigating and will open a > separate issue about this problem). -- 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