You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2016/11/03 21:19:58 UTC

[jira] [Resolved] (STORM-2076) Supervisor sync-processes and sync-supervisor race when downloading new topology code.

     [ https://issues.apache.org/jira/browse/STORM-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stig Rohde Døssing resolved STORM-2076.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.3

This should no longer be an issue with the new supervisor https://github.com/apache/storm/pull/1747

> Supervisor sync-processes and sync-supervisor race when downloading new topology code.
> --------------------------------------------------------------------------------------
>
>                 Key: STORM-2076
>                 URL: https://issues.apache.org/jira/browse/STORM-2076
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.0.2
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>             Fix For: 1.0.3
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The fix for https://issues.apache.org/jira/browse/STORM-1934 moved the cleanup of topology code to sync-processes. The cleanup is based on ls-local-assignment, but this is not called from sync-supervisor until all the new topology code has been downloaded. As a result, sync-processes may delete new topology code before sync-supervisor has had a chance to update ls-local-assignment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)