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

Gergely Novák commented on YARN-6894:
-------------------------------------

It's kind of logical, that if you define the _queue_ parameter you wish to see 
the applications actually in the queue. As I see it, there might be several 
possible solutions:
# Update the documentation to something like this: "queue - applications that 
are currently in this queue"
# Return all the applications that were submitted to that queue 
# Introduce another query parameter that returns all the applications that were 
submitted to a queue

Any thoughts?

> RM Apps API returns only active apps when query parameter queue used
> --------------------------------------------------------------------
>
>                 Key: YARN-6894
>                 URL: https://issues.apache.org/jira/browse/YARN-6894
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, restapi
>            Reporter: Grant Sohn
>            Priority: Minor
>
> If you run RM's Cluster Applications API with no query parameters, you get a 
> list of apps.
> If you run RM's Cluster Applications API with any query parameters other than 
> "queue" you get the list of apps with the parameter filters being applied.
> However, when you use the "queue" query parameter, you only see the 
> applications that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, 
> ACCEPTED, RUNNING).  This behavior is inconsistent with the API.  If there is 
> a sound reason behind this, it should be documented and it seems like there 
> might be as the mapred queue CLI behaves similarly.
> http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to