You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Rama Chavali (JIRA)" <ji...@apache.org> on 2018/08/20 06:52:00 UTC
[jira] [Issue Comment Deleted] (CURATOR-477) Ability to turn off Zk
Watches in Curator Framework
[ https://issues.apache.org/jira/browse/CURATOR-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rama Chavali updated CURATOR-477:
---------------------------------
Comment: was deleted
(was: The corresponding Curator PR is here https://github.com/apache/curator/pull/277)
> Ability to turn off Zk Watches in Curator Framework
> ---------------------------------------------------
>
> Key: CURATOR-477
> URL: https://issues.apache.org/jira/browse/CURATOR-477
> Project: Apache Curator
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.1
> Reporter: Rama Chavali
> Priority: Major
>
> In our use case, we use *{{TreeCache}}* to get Zk Data periodically. We start *{{TreeCache}}* read data and close it. In this use case, The {{ZkWatchManager}} of {{ZooKeeper}} class keeps growing for every TreeCache operation because new {{TreeNode}} objects are created and added there leading to a memory leak. Also since we do not want the Watcher to periodically watch, this creates unnecessary background operations.
> Can we introduce a builder flag in CuratorFramework's Builder some thing called "createZkWatches" that we can use to turn the watchers off? The default would be set to true to retain the current behaviour.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)