Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper >> mail # user >> ClientCnxn$EventThread leak?


+
Jun Rao 2011-01-25, 17:18
+
Jean-Daniel Cryans 2011-01-25, 17:24
+
Fournier, Camille F. [Tec... 2011-01-25, 17:31
Copy link to this message
-
Re: ClientCnxn$EventThread leak?
Thanks, it seems the issue disappeared in 3.3.2, likely fixed by
https://issues.apache.org/jira/browse/ZOOKEEPER-795

Jun

On Tue, Jan 25, 2011 at 9:31 AM, Fournier, Camille F. [Tech] <
[EMAIL PROTECTED]> wrote:

> I think this might be a side-effect of
> https://issues.apache.org/jira/browse/ZOOKEEPER-794 which does slightly
> change the code in the ClientCnxn$EventThread run().
>
> -----Original Message-----
> From: Jun Rao [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 25, 2011 12:19 PM
> To: [EMAIL PROTECTED]
> Subject: ClientCnxn$EventThread leak?
>
> Hi,
>
> I am using ZK 3.3.0 and observed a thread leaking problem. In the ZK
> watcher, when there is a session expiration event, we close the old ZK
> client and create a new one. I observed that every time we get a ZK session
> expire event, one more ClientCnxn$EventThread thread is added. On the other
> hand, there is alway 1 ClientCnxn$SendThread, no matter how many times a
> session has expired. If our code caused the thread leak, I'd expect that
> both ClientCnxn$EventThread and ClientCnxn$SendThread to increase over
> time.
> Is there a known thread leaking problem in ZK? Thanks,
>
> Jun
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB