[
https://issues.apache.org/jira/browse/CURATOR-233?focusedWorklogId=791719&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-791719
]
ASF GitHub Bot logged work on CURATOR-233:
------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jul/22 06:34
Start Date: 17/Jul/22 06:34
Worklog Time Spent: 10m
Work Description: tisonkun commented on PR #207:
URL: https://github.com/apache/curator/pull/207#issuecomment-1186419107
This seems like a duplicate of
[CURATOR-536](https://issues.apache.org/jira/browse/CURATOR-536) and should be
fixed by https://github.com/apache/curator/pull/322. Closed as completed. Feel
free to file another ticket if it's not the case.
Issue Time Tracking
-------------------
Worklog Id: (was: 791719)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Priority: Major
> Fix For: TBD
>
> Attachments: DoubleBarrierClient.java, DoubleBarrierTester.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
