storm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STORM-312) 'storm monitor' to monitor throughput performance interactively
Date Mon, 07 Jul 2014 19:23:35 GMT


ASF GitHub Bot commented on STORM-312:

Github user danehammer commented on a diff in the pull request:
    --- Diff: storm-core/src/clj/backtype/storm/command/monitor.clj ---
    @@ -0,0 +1,37 @@
    +;; Licensed to the Apache Software Foundation (ASF) under one
    +;; or more contributor license agreements.  See the NOTICE file
    +;; distributed with this work for additional information
    +;; regarding copyright ownership.  The ASF licenses this file
    +;; to you under the Apache License, Version 2.0 (the
    +;; "License"); you may not use this file except in compliance
    +;; with the License.  You may obtain a copy of the License at
    +;; Unless required by applicable law or agreed to in writing, software
    +;; distributed under the License is distributed on an "AS IS" BASIS,
    +;; WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +;; See the License for the specific language governing permissions and
    +;; limitations under the License.
    +(ns backtype.storm.command.monitor
    +  (:use [ :only [cli]])
    +  (:use [backtype.storm thrift config log])
    --- End diff --
    I know we're trying to move to more idiomatic clojure, so here it'd be more readable to
specify what you're using (which it looks like you're not using very much from each of these).

> 'storm monitor' to monitor throughput performance interactively
> ---------------------------------------------------------------
>                 Key: STORM-312
>                 URL:
>             Project: Apache Storm (Incubating)
>          Issue Type: New Feature
>            Reporter: Jiahong Li
>              Labels: cmd-line-monitor
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> This cmd line tool 'storm monitor' will use Nimbus.Client to get throughput information
from Nimbus Server.
> 1)One can specify topology's name, component's name to monitor it's throughput interactively.
> 2) It will statistics 'emit' and/or 'transferred' throughput in a given time window and
print it in a given time frequency
> The implementation will be much like yahoo's storm-perf-test (

This message was sent by Atlassian JIRA

View raw message