incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Morel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (S4-65) Create s4 status command
Date Wed, 11 Jul 2012 14:52:34 GMT

    [ https://issues.apache.org/jira/browse/S4-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411596#comment-13411596
] 

Matthieu Morel commented on S4-65:
----------------------------------

About standby nodes info: I checked that this was not a regression. Failover properly works
even though standby nodes do not publish information in Zookeeper. It could be an interesting
feature to have though. In the meantime, you can probably skip that information until we add
it.

About appId: I created S4-76 and will fix it as soon as I can. Just ignore that id.
                
> Create s4 status command
> ------------------------
>
>                 Key: S4-65
>                 URL: https://issues.apache.org/jira/browse/S4-65
>             Project: Apache S4
>          Issue Type: Sub-task
>    Affects Versions: 0.5
>            Reporter: Matthieu Morel
>            Assignee: Aimee Cheng
>             Fix For: 0.5
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message