increasing nimbus.task.timeout.secs: 30 to higher value has solved the problem
On Thu, Mar 19, 2015 at 1:17 PM, Tousif <[email protected]> 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.zookeeper.session.timeout: 60000 > storm.zookeeper.connection.timeout: 50000 > > On Thu, Mar 19, 2015 at 11:59 AM, Tousif <[email protected]> wrote: > >> 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.ClientCnxn [INFO] Client session timed out, >> have not heard from server in 28592ms for sessionid 0x24c2791ecfd0019, >> closing socket connection and attempting reconnect >> 2015-03-19 00:40:47 s.k.KafkaUtils [WARN] No data found in Kafka >> Partition partition_1 >> 2015-03-19 00:40:47 o.a.z.ClientCnxn [INFO] Client session timed out, >> have not heard from server in 28582ms for sessionid 0x14c2791ecf40011, >> closing socket connection and attempting reconnect >> 2015-03-19 00:40:47 o.a.z.ClientCnxn [INFO] Client session timed out, >> have not heard from server in 28601ms for sessionid 0x14c2791ecf40013, >> closing socket connection and attempting reconnect >> 2015-03-19 00:40:47 o.a.z.ClientCnxn [INFO] Client session timed out, >> have not heard from server in 28599ms for sessionid 0x34c2791efa40011, >> closing socket connection and attempting reconnect >> >> >> -- >> >> >> Regards >> Tousif Khazi >> >> > > > -- > > > Regards > Tousif Khazi > > -- Regards Tousif Khazi
