curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dkesler <>
Subject [GitHub] curator pull request: Curator 187
Date Mon, 09 Feb 2015 21:22:15 GMT
GitHub user dkesler opened a pull request:

    Curator 187

    A fix for the problem described in
 The ChildReaper continuously runs even when its Reaper is not the leader, resulting in a
pileup of paths to reap in the Reaper's queue. 
    This changeset allows the ChildReaper to create the LeaderLatch so that it too can avoid
doing any work (i.e. adding paths to the Reaper's queue) if this application is not the leader.

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

    $ git pull CURATOR-187

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 #66
commit 520ae54ac4a49292201417fa6b1104cf579704d3
Author: David Kesler <>
Date:   2015-02-09T18:19:20Z

    Adding a new constructor to Reaper so that it can optionally take a fully constructed
leader latch that is owned by another class rather than create its own leader latch

commit 9da79604bfe7e775d1d42a25f0ac7579b8ee0464
Author: David Kesler <>
Date:   2015-02-09T18:25:51Z

    Reaper now sets its initial reapingIsActive state based on the state of the leader latch
in case the leader latch was already started before being passed into the reaper's constructor

commit 49eb02a04f377a3b9e2da3b3904311ddddf1aa9d
Author: David Kesler <>
Date:   2015-02-09T18:50:39Z

    ChildReaper now creates a leaderLatch itself if a leader path is provided and does no
work (such as passing paths to its Reaper) if it is not currently the leader.


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