[
https://issues.apache.org/jira/browse/STORM-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353407#comment-15353407
]
Satish Duggana commented on STORM-1933:
---------------------------------------
I was working on an issue where a race condition occurs in removing topology
for a worker which is already started but it fails because of topology gets
deleted by sync-supervisor. sync-supervisor should never kill any topology. It
should simply raise sync-process event and add it to syncProcessManager which
is already done by sync-supervisor. Removing topologies should be done by the
same thread which kills topologies. So, Killing(because they do not exist any
more or rebalanced existing topologies) and removing invalid topologies should
be done only by sync-process. I agree that this solution would avoid these kind
of scenarios.
> Intermittent test failure on test-multiple-active-storms-multiple-supervisors
> for supervisor-test
> --------------------------------------------------------------------------------------------------
>
> Key: STORM-1933
> URL: https://issues.apache.org/jira/browse/STORM-1933
> Project: Apache Storm
> Issue Type: Sub-task
> Components: storm-core
> Affects Versions: 1.0.0, 2.0.0, 1.0.1
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Attachments:
> only-thread-1362-and-1363-BUG-60850-intermittent-failure-supervisor-test.txt
>
>
> test-multiple-active-storms-multiple-supervisors is failing with fairly high
> chance. I've run unit test of 1.x branch 3 times and met this issue, and
> users report FileNotFound issue on supervisor which seems to be related to
> this.
> I have log file so I'll attach once issue is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
