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

["Shiliang Cao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249466#comment-15249466 ] 

Shiliang Cao commented on CURATOR-233:
--------------------------------------

Hi [~randgalt] and [~mdrob], Very glad to see this bug fixed in 2.10.1, thanks for the effort of all you guys.

This bug caused some blocker issue in our coprhd project, I'm thinking to upgrade curator to 2.10.1 as soon as possible ... so my question is when 2.10.1 will be available? Thanks a lot!

> 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: 2.10.1, 3.1.1
>
>         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.4#6332)