[
https://issues.apache.org/jira/browse/STORM-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354765#comment-15354765
]
ASF GitHub Bot commented on STORM-1934:
---------------------------------------
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1528
Note: This patch removes the change from STORM-1561 since supervisor
originally checks the change of executors in same port.
Please refer `read-allocated-workers` and `matches-an-assignment?`, and let
me know if I'm missing here.
> Race condition between sync-supervisor and sync-processes raises several
> strange issues
> ---------------------------------------------------------------------------------------
>
> Key: STORM-1934
> URL: https://issues.apache.org/jira/browse/STORM-1934
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.0, 2.0.0, 1.0.1
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Critical
>
> There're some strange issues including STORM-1933 and others (which I will
> file an issue soon) which are related to race condition in supervisor.
> As I mentioned to STORM-1933, basically sync-supervisor relies on zk
> assignment, and sync-processes relies on local assignment and local workers
> directory, but in fact sync-supervisor also access local state and take some
> actions which affects sync-processes. And also Satish left the comment to
> STORM-1933 describing other issue related to race condition and idea to fix
> this which is same page on me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
