curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <>
Subject [jira] [Updated] (CURATOR-233) Bug in double barrier
Date Mon, 24 Aug 2015 21:30:46 GMT


Mike Drob updated CURATOR-233:
    Fix Version/s:     (was: awaiting-response)

[~Lianro] - Please check out my pull request, I think it solves the problem that you are experiencing.
The unit test I included is a much simplified version of your use case, but I think it still
covers the necessary code paths.

I have not tested this with 3+ clients, which will be necessary to make sure that the notifications
are properly handled. It works with 2 clients, though.

> Bug in double barrier
> ---------------------
>                 Key: CURATOR-233
>                 URL:
>             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:,
> 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

View raw message