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

Posted to dev@storm.apache.org by "Derek Dagit (JIRA)" <ji...@apache.org> on 2015/01/22 17:38:34 UTC

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

Derek Dagit created STORM-636:
---------------------------------

             Summary: 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
    Affects Versions: 0.10.0
            Reporter: Derek Dagit
            Assignee: Derek Dagit
            Priority: Minor


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)