Overby (groverby) grove...@cisco.com, user@storm.apache.org
user@storm.apache.org
Subject: Re: Supervisor believes worker has not started.
Which version of storm are you using?
--
Harsha
On June 2, 2015 at 8:04:48 AM, Grant Overby (groverby) (grove...@cisco.com)
wrote:
Same here
Subject: Re: Supervisor believes worker has not started.
ld not find a workaround. In my case, the w
, 2015 at 11:24 AM
To: Grant Overby (groverby) grove...@cisco.commailto:grove...@cisco.com,
user@storm.apache.orgmailto:user@storm.apache.org
user@storm.apache.orgmailto:user@storm.apache.org
Subject: Re: Supervisor believes worker has not started.
Which version of storm are you using?
--
Harsha
I ran into this problem and could not find a workaround. In my case, the
worker does not commit suicide, just that the supervisor believes the
worker is dead. Here is the output from one of the supervisor:
2015-06-02T05:56:47.355+ b.s.d.supervisor [INFO] Downloading code for
storm id
Supervisor is reporting that the worker “still hasn’t started” and eventually
kills and restarts the worker. However; the worker has started and is
processing tuples. This repeats indefinitely.
Debugging steps?
When you look at the worker logs, do some of the workers sometimes kill
themselves because there is a missing stormconf.ser file? If so, grab that
error message and have fun googling.
Some will say those problems went away with the latest release.
Apparently, it is complicated.
My best advice
