[jira] [Updated] (STORM-636) UI/Monitor is slow for topologies with a large number of components

["Rick Kellogg (JIRA)" <ji...@apache.org>]

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

Rick Kellogg updated STORM-636:
-------------------------------
    Component/s: storm-core

> UI/Monitor is slow for topologies with a large number of components
> -------------------------------------------------------------------
>
>                 Key: STORM-636
>                 URL: https://issues.apache.org/jira/browse/STORM-636
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 0.10.0
>            Reporter: Derek Dagit
>            Assignee: Derek Dagit
>            Priority: Minor
>             Fix For: 0.10.0
>
>
> The getTopologyInfo method in nimbus fetches from ZK all errors reported by all components.  This becomes too slow for topologies with a larger numbers of components  (bolts/spouts).
> In one example, the UI consistently took over 5 minutes to load the topology page for a topology with nearly 500 components while ZK was under load.
> Errors are currently stored in ZooKeeper under individual znodes per component.  This means that each call to getTopologyInfo needs to list children of each znode and then download the error znodes it finds.



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