Haibo Chen commented on YARN-6058:

This showed up while I was exploring replacing JHS with python scripts (will be 
YARN UI2-like thing) + ATSv2. This is no good story in ATSv2 that supports 
client retrieval of all jobs (flow->flow run-> apps does not work without user 

I think in MR's use case, a limit param on the query would be good enough.  The 
application id, in YARN's case, contains cluster timestamp + the current app 
counter that increments each time. We may be able to leverage that information 
to support time-range queries as well.

> Support for listing all applications i.e /apps
> ----------------------------------------------
>                 Key: YARN-6058
>                 URL: https://issues.apache.org/jira/browse/YARN-6058
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>            Priority: Critical
> Primary use case for /apps is many execution engines runs on top of YARN 
> example, Tez, MR. These engines will have their own UI's which list specific 
> type of entities which are published by them Ex: DAG entities. 
> But, these UI's do not aware of either userName or flowName or applicationId 
> which are submitted by these engines.
> Currently, given that user do not aware of user, flownName, and 
> applicationId, then he can not retrieve any entities. 
> By supporting /apps with filters, user can list of application with given 
> ApplicationType. These applications can be used for retrieving engine 
> specific entities like DAG. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to