@storm.incubator.apache.org
Subject: Re: Workers constantly restarted due to session timeout
1) Is it appropriate to run Zookeeper in parallel on the same node with the
storm services?
I recommend separate, and even then to ZK storage to a path on its own disk
device if possible. ZK
see Storm uses zookeeper-3.3.3 as its
client. Should we downgrade our installation?
Date: Sat, 31 May 2014 13:50:57 -0500
From: der...@yahoo-inc.com
To: user@storm.incubator.apache.org
Subject: Re: Workers constantly restarted due to session timeout
Are you certain
uses zookeeper-3.3.3 as its
client. Should we downgrade our installation?
Date: Sat, 31 May 2014 13:50:57 -0500
From: der...@yahoo-inc.com
To: user@storm.incubator.apache.org
Subject: Re: Workers constantly restarted due to session timeout
Are you certain that nimbus.task.timeout.secs
Subject: Re: Workers constantly restarted due to session timeout
OK, so GC is probably not the issue.
Specifically, this is a connection timeout to ZK from the worker, and it is
resulting in nimbus removing it from the assignments for that node. In turn,
the supervisor reads the schedule
...@yahoo-inc.com
To: user@storm.incubator.apache.org
Subject: Re: Workers constantly restarted due to session timeout
OK, so GC is probably not the issue.
Specifically, this is a connection timeout to ZK from the worker, and it is
resulting in nimbus removing it from the assignments
to make our topology more
resilient to these restarts?
Michael
Date: Fri, 23 May 2014 15:50:50 -0500
From: der...@yahoo-inc.com
To: user@storm.incubator.apache.org
Subject: Re: Workers constantly restarted due to session timeout
2) Is this expected behavior for Storm to be unable to keep up
Subject: Re: Workers constantly restarted due to session timeout
2) Is this expected behavior for Storm to be unable to keep up with
heartbeat threads under high CPU or is our theory incorrect?
Check your JVM max heap size (-Xmx). If you use too much, the JVM will
garbage-collect
2) Is this expected behavior for Storm to be unable to keep up with heartbeat
threads under high CPU or is our theory incorrect?
Check your JVM max heap size (-Xmx). If you use too much, the JVM will
garbage-collect, and that will stop everything--including the thread whose job
it is to do