Re: ZooKeeper + Curator memory usage & data size

[Jordan Zimmerman]

1.1.15 is old. Try 1.3.2 (the latest).

-Jordan

On Feb 15, 2013, at 7:41 AM, sftho...@gmail.com wrote:

Hi,

 

I have started using Curator 1.1.15 to get global locks for synchronisation, on a 3-node ZooKeeper (3.4.4) ensembe. What I noticed was that the data size seems to be growing continuously, as well as the heap usage on the ZooKeeper nodes.

So I set up a test (this time with 1.3.2) where I constantly get & release random lock paths, and monitored data size & heap usage via JMX. This little experiment confirmed my previous findings, both metrics are growing by time, and do not fall back, even if I stop the clients.

According to the Reaper/ChildReaper wiki page, Curator is taking care of cleaning up parent nodes, which suggests that the data size should be proportional to the concurrently locks being held, or at least it should not grow if the average throughput is the same.

Since I could not find anything similar on the forums, it makes me believe I did something worng - can I someone please point me in the right direction?

 

Thanks,

Tamas

--
You received this message because you are subscribed to the Google Groups "curator-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to curator-user...@googlegroups.com.
To post to this group, send email to curato...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/curator-users/-/ApT5zH38OPsJ.
For more options, visit https://groups.google.com/groups/opt_out.