zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JonathanO <...@git.apache.org>
Subject [GitHub] zookeeper pull request #465: ZOOKEEPER-2930: Leader cannot be elected due to...
Date Thu, 15 Feb 2018 13:04:04 GMT
GitHub user JonathanO opened a pull request:

    https://github.com/apache/zookeeper/pull/465

    ZOOKEEPER-2930: Leader cannot be elected due to network timeout of some members.

    Backported to 3.4 from the ZOOKEEPER-2930 branch.
    
    Move sock.connect() into the async connection worker thread.
    Moved a load of connectOne(sid) into the async connection worker thread.
    Use use the async connection worker for all connections.
    This prevents connection delays blocking notifications to other nodes.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/transferwise/zookeeper branch-3.4-ZOOKEEPER-2930

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/465.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #465
    
----
commit ca05df6049e3282fef9fd3f34d07337011b5f4f6
Author: Jonathan Oddy <jonathan.oddy@...>
Date:   2018-02-15T12:22:24Z

    ZOOKEEPER-2930: Leader cannot be elected due to network timeout of some members.
    
    Backported from 3.5.
    
    Move sock.connect() into the async connection worker thread.
    Moved a load of connectOne(sid) into the async connection worker thread.
    Use use the async connection worker for all connections.
    This prevents connection delays blocking notifications to other nodes.

----


---

Mime
View raw message