[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872483#comment-13872483
]
Patrick Hunt commented on ZOOKEEPER-442:
----------------------------------------
I also tried running the same experiment while monitoring the free memory of
the ZK Server. I started a standalone zk server with 15m max/initial memory and
used jconsole to monitor heap usage while running the
zookeeper-removewatches-ex client. With the remove watch call the heap stayed
flat over time, 30 minutes or so, after an initial warm up period. (w/o the
remove call the server quickly fails with oom exception)
Today I plan to add a few more types of remove call scenarios to my simple
client and verify things are handled properly, however things look good at the
moment. I'll try and see if I can dig up my copy of yourkit as well.
Only other thing I see left is to finalize the code review feedback (I hope to
do additional code review later today). Anyone else that can help with this
would be appreciated.
> need a way to remove watches that are no longer of interest
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-442
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: java client, server
> Reporter: Benjamin Reed
> Assignee: Rakesh R
> Priority: Critical
> Fix For: 3.5.0
>
> Attachments: Remove Watch API.pdf, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch
>
>
> currently the only way a watch cleared is to trigger it. we need a way to
> enumerate the outstanding watch objects, find watch events the objects are
> watching for, and remove interests in an event.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
