incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Morel (JIRA)" <>
Subject [jira] [Commented] (S4-65) Create s4 status command
Date Mon, 16 Jul 2012 09:36:35 GMT


Matthieu Morel commented on S4-65:

Brilliant, exactly what we needed!

However I wonder if you could update the patch with the following:
- it seems you are using tabs instead of spaces, which causes trouble in diffs. See the 2
last sections in 
- small suggestions for the command help, in order to clarify that app,stream and cluster
correspond to filters: 
{code}    -app           Only show status of specified S4 application(s)
    -c, -cluster   Only show status of specified S4 cluster(s)
    -gradleOpts    gradle system properties (as in GRADLE_OPTS environment
                   properties) passed to gradle scripts
                   Default: []
    -help          usage
                   Default: false
    -s, -stream    Only show status of specified published stream(s){code}

Many thanks!
> Create s4 status command
> ------------------------
>                 Key: S4-65
>                 URL:
>             Project: Apache S4
>          Issue Type: Sub-task
>    Affects Versions: 0.5
>            Reporter: Matthieu Morel
>            Assignee: Aimee Cheng
>             Fix For: 0.5
>         Attachments: add-s4-status-command.patch
> We should have an "s4 status" command that provides nicely formatted information about
the state of S4 application coordinated through a given Zookeeper ensemble.
> In particular:
> - which applications are deployed
> - on which S4 nodes these applications are deployed
> - how many S4 nodes are running, how many S4 nodes are in standby
> - which streams are published, which applications are connected
> The implementation would probably add a new class in the s4-tools project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message