GitHub user htuy42 opened a pull request:
https://github.com/apache/curator/pull/270
A fix for double barrier timeout behavior, and an accompanying test
Assuming this is the desired behavior (ie once we timeout we are no longer
considered to be in the barrier), this fix will work. By the time the method
returns false, we will no longer be considered a member waiting at the barrier,
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/htuy42/curator CURATOR-318
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/270.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 #270
----
commit 7a64aa2eaa6c4a85a9ad7b95aa83cc1bbde43b8b
Author: BuildTools <42jpattiz@...>
Date: 2018-07-14T06:45:51Z
Added a test for double barrier timeout behavior. Also added a fix that
would
remove our node immediately before returning false if we are timing out
----
---
