Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6638918C71 for ; Wed, 20 Apr 2016 08:15:26 +0000 (UTC) Received: (qmail 87315 invoked by uid 500); 20 Apr 2016 08:15:26 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 87248 invoked by uid 500); 20 Apr 2016 08:15:26 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 87217 invoked by uid 99); 20 Apr 2016 08:15:26 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 08:15:26 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B09942C1F54 for ; Wed, 20 Apr 2016 08:15:25 +0000 (UTC) Date: Wed, 20 Apr 2016 08:15:25 +0000 (UTC) From: "Shiliang Cao (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CURATOR-233) Bug in double barrier MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249466#comment-15249466 ] Shiliang Cao edited comment on CURATOR-233 at 4/20/16 8:14 AM: --------------------------------------------------------------- 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! Since curator 3.X requires zookeeper 3.5+, meanwhile, we use zookeeper 3.4.6 and don't have an upgrade plan now, so it seems that curator 2.10.1 is our only option now. was (Author: shiliang): 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! Since curator 3.X requires zookeeper 3.5+, so it seems that curator 2.10.1 is our only option now. > 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)