You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/01 03:48:11 UTC

[jira] [Commented] (STORM-1934) Race condition between sync-supervisor and sync-processes raises several strange issues

    [ https://issues.apache.org/jira/browse/STORM-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358331#comment-15358331 ] 

ASF GitHub Bot commented on STORM-1934:
---------------------------------------

Github user HeartSaVioR commented on the issue:

    https://github.com/apache/storm/pull/1528
  
    @harshach 
    `sync-supervisor` writes local assignment after code download for topology is completed. 
    Since `sync-processes` launches worker based on local assignment, there's a guarantee that code download is completed before launching worker.
    
    Btw, as you see the diff, STORM-130 is not on recent code. Not sure why it's removed.


> 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)