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

Li Lu commented on YARN-5561:
-----------------------------

Thanks [~rohithsharma], the two proposed APIs make the app - attempt - 
container APIs more comprehensive. LGTM. 

bq. are looking for a complete applications page where all applications which 
were running/completed had to be listed.
This is something I'm not sure if we'd like to support on the timeline level. 
This information is pretty much available on the RM side via the state store. 
Why do we want to encourage an expensive operation on the timeline store for 
this data? 

> [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and 
> entities via REST
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-5561
>                 URL: https://issues.apache.org/jira/browse/YARN-5561
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-5561.patch, YARN-5561.v0.patch
>
>
> ATSv2 model lacks retrieval of {{list-of-all-apps}}, 
> {{list-of-all-app-attempts}} and {{list-of-all-containers-per-attempt}} via 
> REST API's. And also it is required to know about all the entities in an 
> applications.
> It is pretty much highly required these URLs for Web  UI.
> New REST URL would be 
> # GET {{/ws/v2/timeline/apps}}
> # GET {{/ws/v2/timeline/apps/\{app-id\}/appattempts}}.
> # GET 
> {{/ws/v2/timeline/apps/\{app-id\}/appattempts/\{attempt-id\}/containers}}
> # GET {{/ws/v2/timeline/apps/\{app id\}/entities}} should display list of 
> entities that can be queried.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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