You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2014/11/20 16:57:34 UTC

[jira] [Updated] (STORM-562) When Isolated topologies are running "free slots" can be wrong/misleading

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

Robert Joseph Evans updated STORM-562:
--------------------------------------
    Summary: When Isolated topologies are running "free slots" can be wrong/misleading  (was: Whne Isolated topologies are running "free slots" can be wrong/misleading)

> When Isolated topologies are running "free slots" can be wrong/misleading
> -------------------------------------------------------------------------
>
>                 Key: STORM-562
>                 URL: https://issues.apache.org/jira/browse/STORM-562
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.9.3
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>
> The isolation scheduler will blacklist a node so that other topologies cannot run on it, but this is not reflected anywhere in the UI, and makes it difficult to know how full a cluster is.
> I propose that we add in a new concept to the scheduler.  Where it can "claim" a slot for a topology without actually running anything on that slot.  We would then reflect the number of claimed slots in thrift interface and in the UI.



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