You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Zili Chen (Jira)" <ji...@apache.org> on 2022/07/17 06:36:00 UTC

[jira] [Closed] (CURATOR-233) Bug in double barrier

     [ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zili Chen closed 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
>            Priority: Major
>         Attachments: DoubleBarrierClient.java, DoubleBarrierTester.java
>
>          Time Spent: 20m
>  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)