[ https://issues.apache.org/jira/browse/CURATOR-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585491#comment-16585491 ]
ASF GitHub Bot commented on CURATOR-477: ---------------------------------------- Github user ramaraochavali commented on the issue: https://github.com/apache/curator/pull/277 @Randgalt @dragonsinth on a second thought, I think just cleaner to it at the `TreeCache` level. So closing this PR and opening a fresh PR for it with correct branch name as well. The correct PR is https://github.com/apache/curator/pull/278 > 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)