[
https://issues.apache.org/jira/browse/YARN-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732142#comment-13732142
]
Zhijie Shen commented on YARN-696:
----------------------------------
Thanks for supporting multiple states params. Here're two comments:
1. The states params don't need to be parsed every time when comparing with new
iterated RMApp. Do it once before the loop.
2. bq. Are there any examples where an application can be created with a
predefined static state?
Maybe you want to schedule some event explicitly, and use waitForState() to
wait for a RMApp's reaching a desired state. See the example in
TestRMWebServicesApps#testMultipleAppAttempts
> Enable multiple states to to be specified in Resource Manager apps REST call
> ----------------------------------------------------------------------------
>
> Key: YARN-696
> URL: https://issues.apache.org/jira/browse/YARN-696
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 2.0.4-alpha
> Reporter: Trevor Lorimer
> Assignee: Trevor Lorimer
> Priority: Trivial
> Attachments: YARN-696.diff
>
>
> Within the YARN Resource Manager REST API the GET call which returns all
> Applications can be filtered by a single State query parameter (http://<rm
> http address:port>/ws/v1/cluster/apps).
> There are 8 possible states (New, Submitted, Accepted, Running, Finishing,
> Finished, Failed, Killed), if no state parameter is specified all states are
> returned, however if a sub-set of states is required then multiple REST calls
> are required (max. of 7).
> The proposal is to be able to specify multiple states in a single REST call.
--
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
