hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6058) Support for listing all applications i.e /apps
Date Thu, 12 Jan 2017 03:22:16 GMT

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

Rohith Sharma K S commented on YARN-6058:

+1 for flow type which is very much necessary. 
There are 2 pieces 
#  When a workflow is submitted by Oozie which has many actions(MR, Tez, Spak), then flow
type should be Oozie. Always better to consider submitter as flow type. It can not be a Union
of all applications type because each run can have different execution engine. 
# */apps* is also required because every execution framework has their own UI.(JHS for MR,
Tez). These frameworks render entities of respective framework. Say, Oozie submits (MR,Tez)
actions then Tez UI renders  DAG of Oozie Tez. And similarly, JHS renders job details of Oozie
MR. Such cases, */apps* help to get those applications directly rather than going through

> 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
>              Labels: yarn-5355-merge-blocker
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message