You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "James Xu (JIRA)" <ji...@apache.org> on 2013/12/14 17:05:07 UTC

[jira] [Created] (STORM-112) Race condition between Topology Kill and Worker Timeout can crash supervisor

James Xu created STORM-112:
------------------------------

             Summary: Race condition between Topology Kill and Worker Timeout can crash supervisor
                 Key: STORM-112
                 URL: https://issues.apache.org/jira/browse/STORM-112
             Project: Apache Storm (Incubating)
          Issue Type: Bug
            Reporter: James Xu


Recently during testing on a single node cluster we saw a supervisor crash when a topology was killed. The supervisor came back up and recovered, so it was not that big of a deal, but when we dug into it, it appears that there is a race.
https://github.com/nathanmarz/storm/issues/656

When a topology is killed the local assignments are reset, and then stormconf.ser is deleted right away. But at the same time sync-process may already be running with old state indicating that a worker timed out and needs to be relaunched. launch-worker then tries to read in the topology conf which was deleted and crashes.

The following is a sanitized version of the supervisor log that shows this happening.
https://gist.github.com/revans2/6282830



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)