Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Wed, 26 Aug 2015 04:47:45 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12844395.1436650880000.167046.1440564465659@Atlassian.JIRA>
In-Reply-To: <JIRA.12844395.1436650880000@Atlassian.JIRA>
References: <JIRA.12844395.1436650880000@Atlassian.JIRA>
 <JIRA.12844395.1436650880713@arcas>
Subject: [jira] [Commented] (CURATOR-233) Bug in double barrier
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jordan Zimmerman commented on CURATOR-233:
------------------------------------------

Can this be pushed out to 2.9.1 (or 2.10.0)?

> 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.9.0
>
>         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)