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

Aimee Cheng commented on S4-65:
-------------------------------

There are some questions I met:

1. For the third one in description: "how many S4 nodes are running, how many 
S4 nodes are in standby", it seems the standby nodes didn't register 
information in Zookeeper, and they only listen the change of znode. So maybe 
need to add some information to zookeeper, or are there some other ways to get 
the information of standby nodes?

2. When publishing streams, I saw the information on consumer/publisher as 
follow: 
get /s4/streams/names/consumers/consumer-0000000002

{
  "id": "names/cluster1/-1",
  "simpleFields": {
    "appId": "-1",
    "clusterName": "cluster1"
  },
  "listFields": {},
  "mapFields": {}
}
I am confused by the appId in "-1". Though from S4-71 I saw that there would be 
only 1 app running in a subcluster and I can get the app name when know the 
cluster name, I want to know the meaning of appId here.

                
> 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

        

Reply via email to