increasing nimbus.task.timeout.secs: 30 to higher value has solved the
problem
On Thu, Mar 19, 2015 at 1:17 PM, Tousif wrote:
> and here are config from storm.yaml
>
> supervisor.worker.start.timeout.secs: 300
> supervisor.worker.timeout.secs: 60
> nimbus.task.timeout.secs: 30
> storm.zooke
and here are config from storm.yaml
supervisor.worker.start.timeout.secs: 300
supervisor.worker.timeout.secs: 60
nimbus.task.timeout.secs: 30
storm.zookeeper.session.timeout: 6
storm.zookeeper.connection.timeout: 5
On Thu, Mar 19, 2015 at 11:59 AM, Tousif wrote:
> Hello,
>
> I see
Hello,
I see 1 worker on each supervisor node working for some period of time and
than workers disconnects and all three workers started on one single
supervisor.
I have 3 node zk, 3 kafka brokers and 3 supervisors .
i see these messages . Any config i need to tune?
2015-03-19 00:40:47 o.a.z.
