curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper
Date Mon, 02 Jun 2014 23:05:01 GMT


ASF GitHub Bot commented on CURATOR-110:

GitHub user cammckenzie opened a pull request:

    Curator 110

    Fix for CURATOR-110

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

    $ git pull CURATOR-110

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

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

    This closes #9
commit 1a63a102ebbaaead265babd71a3d52928f848bd0
Author: Cameron McKenzie <>
Date:   2014-06-02T06:30:26Z

    CURATOR-110 - Modified state handling to treat 'CONNECTED' and
    'RECONNECTED' events in the same way. Added a test case for the leader
    latch being started before a connection to ZK has been established.

commit 0b7ae7e3672a9c817fe31144cd6b18d9a357f124
Author: Cameron McKenzie <>
Date:   2014-06-02T23:01:31Z

    CURATOR-110 - Fixed up formatting to Curator standards


> LeaderLatch does not complete if it is started without a connection to ZooKeeper
> --------------------------------------------------------------------------------
>                 Key: CURATOR-110
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.5.0
>            Reporter: Cameron McKenzie
>            Priority: Minor
>              Labels: connection, latch, leader
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> Given the following conditions:
> 1.) No connection is available to ZK
> 2.) A LeaderLatch is created and started
> 3.) All retries for the leader latch creating its ephemeral zNode have been exhausted.
> At this point the LeaderLatch will not begin functioning correctly when a connection
is established. This is due to it ignoring 'CONNECTED' connection state events (it only handles
> The fix should simply be a case of making the state handling for CONNECTED and RECONNECTED
the same.

This message was sent by Atlassian JIRA

View raw message