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/10/05 05:51:00 UTC

[jira] [Commented] (CURATOR-654) DistributedBarrier watcher leak

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

Zili Chen commented on CURATOR-654:
-----------------------------------

Hi [~sscott]! Thanks for your reporting. You can directly send a pull request against the GitHub repository https://github.com/apache/curator. And please add a test case to the patch.

> DistributedBarrier watcher leak
> -------------------------------
>
>                 Key: CURATOR-654
>                 URL: https://issues.apache.org/jira/browse/CURATOR-654
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 5.3.0
>            Reporter: Stuart Scott
>            Priority: Major
>         Attachments: CURATOR-654__Remove_watchers_after_waiting_for_barrier_.patch
>
>
> The DistributedBarrier adds a zookeeper exists watcher in the waitOnBarrier() method. It appears as though the watcher is never removed. In a system where DistributedBarriers are used heavily this eventually results in the system running out of memory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)