zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3378) Set the quorum cnxn timeout independently from syncLimit
Date Tue, 21 May 2019 02:37:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844454#comment-16844454

Hudson commented on ZOOKEEPER-3378:

SUCCESS: Integrated in Jenkins build Zookeeper-trunk-single-thread #365 (See [https://builds.apache.org/job/Zookeeper-trunk-single-thread/365/])
ZOOKEEPER-3378: Set the quorum cnxn timeout independently from syncLimit (eolivelli: rev 6e9802b440b0c706a035a25aafe40b28d25dfadc)
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/QuorumPeer.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/QuorumCnxManager.java
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md

> Set the quorum cnxn timeout independently from syncLimit
> --------------------------------------------------------
>                 Key: ZOOKEEPER-3378
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3378
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: quorum
>            Reporter: Brian Nixon
>            Assignee: Brian Nixon
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>          Time Spent: 20m
>  Remaining Estimate: 0h
> If an ensemble requires a high sync limit to support a large data tree or transaction
rate, it can cause the QuorumCxnManager to hang over-long in response to quorum events. Using
the sync limit for this timeout is a convenience in terms of keeping all failure detection
mechanisms in sync but it is not strictly required for correct behavior.

This message was sent by Atlassian JIRA

View raw message