curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CURATOR-107) Regarding large number of watch count
Date Fri, 23 May 2014 12:57:01 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jordan Zimmerman resolved CURATOR-107.
--------------------------------------

    Resolution: Fixed

Thanks for this. I applied a similar change to LeaderLatch and PathChildrenCache. NOTE: the
PathChildrenCache change may have performance consequences. I'll write a Tech Note on this.

> Regarding large number of watch count
> -------------------------------------
>
>                 Key: CURATOR-107
>                 URL: https://issues.apache.org/jira/browse/CURATOR-107
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.4.1, 2.4.2
>         Environment: ZooKeeper 3.4.6
>            Reporter: Hyun Sik Kang
>              Labels: locks
>             Fix For: 2.5.0
>
>
> It's about issue that zookeeper's watch count is being increased.
> I wrote issue on zookeeper mailing list but I couldn't get cool answer yet.
> Please share any opinion with us if you have an idea..
> http://zookeeper-user.578899.n2.nabble.com/Regarding-large-number-of-watch-count-td7579811.html
> Refer to this article.
> I've used following code for getting and releasing lock
> try {
>  lock.acquire(...);
> } finally {
>  lock.release();
> }
> Please check if I misunderstood how to use curator properly.
> Thank you.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message