[
https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927884#comment-15927884
]
ASF GitHub Bot commented on CURATOR-233:
----------------------------------------
GitHub user jld123 opened a pull request:
https://github.com/apache/curator/pull/207
Fix for CURATOR-233
Fix for CURATOR-233.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jld123/curator CURATOR-233
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/207.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 #207
----
commit 6095937307cd5a18b48d0ce03f9417cd556c062c
Author: jld123 <[email protected]>
Date: 2017-03-16T11:47:46Z
Fix for CURATOR 233
----
> Bug in double barrier
> ---------------------
>
> Key: CURATOR-233
> URL: https://issues.apache.org/jira/browse/CURATOR-233
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 2.8.0
> Reporter: J D
> Assignee: Mike Drob
> Fix For: TBD
>
> Attachments: DoubleBarrierClient.java, DoubleBarrierTester.java
>
>
> Hi,
> I think I discovered a bug in the internalLeave method of the double barrier
> implementation.
> When a client is told to leave the barrier after maxWait it does not do so. A
> flag is set but the client does not leave the barrier, instead it keeps
> iterating through the control loop and drives CPU usage to 100%.
> I have attached an example.
> Best regards
> Lianro
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
