You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2015/07/22 13:44:04 UTC

[jira] [Created] (SOLR-7819) ZkController.ensureReplicaInLeaderInitiatedRecovery does not respect retryOnConnLoss

Shalin Shekhar Mangar created SOLR-7819:
-------------------------------------------

             Summary: 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.1, 5.2
            Reporter: Shalin Shekhar Mangar
             Fix For: 5.3, Trunk


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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org