You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/12/20 08:57:58 UTC

[jira] [Resolved] (STORM-2190) Topology submission blocked behind scheduling

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

Jungtaek Lim resolved STORM-2190.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0
                   2.0.0

Thanks [~revans2], I merged into master and 1.x branches.

> Topology submission blocked behind scheduling
> ---------------------------------------------
>
>                 Key: STORM-2190
>                 URL: https://issues.apache.org/jira/browse/STORM-2190
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 0.10.0, 1.0.0, 2.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>             Fix For: 2.0.0, 1.1.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> The submit-lock in nimbus seems to protect some very large and slow sections of code.  As more and more topologies are submitted scheduling can take longer and longer to complete making submitting a topology take increasingly longer.  But most of scheduling does not need to be protected by this lock.  Only a small section of the scheduler pulls state from zookeeper that the lock protects elsewhere.
> We should split this lock up and protect scheduling separate from protecting StormBase stored in zk.



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