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 Threaded View
Zookeeper >> mail # dev >> SendThread is exitting after OOMError(ZooKeeper-1100)


Copy link to this message
-
Re: SendThread is exitting after OOMError(ZooKeeper-1100)
Can you open a new issue with this?

Thanks,
C

On Tue, Jan 24, 2012 at 4:36 AM, Rakesh R <[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
>
> SendThread is exitting after OOM(ZooKeeper-1100):-
>
>
>
> After reviewing the ClientCnxn code, there is still chances of exiting the SendThread without intimating the users.
>
> Say if client throws OOMError and entered into the throwable block. Here again while sending the Disconnected event, its creating "new WatchedEvent()" object.
>
> This will throw OOMError and leads to exit the SendThread without any Disconnected event notification.
>
>
>
> Earlier we had a discussion reg the OOMError in SendThread. But we didn't notice these and closed the issue.
>
>
>
> try{
>
>    //...
>
> } catch (Throwable e)
>
> {
>
>    //..
>
>    cleanup();
>
>   if(state.isAlive()){
>
>        eventThread.queueEvent(
>
>        new WatchedEvent(Event.EventType.None,  Event.KeeperState.Disconnected, null) )
>
>   }
>
>   //....
>
> }
>
>
>
>
>
> Thanks & Regards,
>
> Rakesh R
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