[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689639#comment-13689639 ]
Vinod Kumar Vavilapalli commented on YARN-791: ---------------------------------------------- okay, I don't see me going back on the default RUNNING state. But to be clear that we are all on the same page, here's the summary - Have both RPC and web-service take in multiple states. -- RPC: a set of states -- web-service: a comma separate list of states - Default for both RPC and the web-service is only RUNNING. -- RPC: --- In proto, not sure we can have default values. If possible, we can give a default RUNNING state. If not we can just document it. --- In java API, we can have two GetClusterNodesRequest.newInstance() methods, one that doesn't take any states, but defaults to RUNNING and one that explicitly takes a set of states. Both should be clear in the javadoc. -- In web-service, we can just document that the default is RUNNING. - For getting all the nodes, we can give all states or invent a new state '*' which returns everything. > Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API > ----------------------------------------------------------------------------- > > Key: YARN-791 > URL: https://issues.apache.org/jira/browse/YARN-791 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, resourcemanager > Affects Versions: 2.0.4-alpha > Reporter: Sandy Ryza > Assignee: Sandy Ryza > Attachments: YARN-791-1.patch, YARN-791-2.patch, YARN-791-3.patch, > YARN-791-4.patch, YARN-791.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira