curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From domwong <>
Subject [GitHub] curator pull request: Curator locks leaving dangling watches
Date Wed, 21 May 2014 12:49:37 GMT
GitHub user domwong opened a pull request:

    Curator locks leaving dangling watches

    As per . I've seen this in our services
    The issue is because the code is using exists() call rather than getData() for creating
a watch for lock. exists() creates a watch regardless of whether the node exists or not, getData()
will only create the watch if node exists

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

    $ git pull master

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 #7
commit 8a94985c07b3e6f74ac1a2935af008cbdb649410
Author: Dominic Wong <>
Date:   2014-05-21T12:20:55Z

    Lock is leaving dangling watchers for nodes that don't exist.

commit c9716499642b2dd4a0d77e5df6f9b84e8dfc90d0
Author: Dominic Wong <>
Date:   2014-05-21T12:40:39Z

    Catch no node exception

commit ac57e11b34bb2970775b385f5a1e94bccd287232
Author: Dominic Wong <>
Date:   2014-05-21T12:45:54Z

    No need for null check


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message