Varun Saxena commented on YARN-5561:

I was also thinking that we can have an endpoint like /ws/v2/applicationhistory.
This can be used to not only serve app attempt.container reports but also serve 
use cases like serving aggregated logs of historical apps. We would need to 
serve aggregated logs from somewhere too. This will be useful for UI as well.

Regarding metrics, well we can always extend ContainerInfo to carry metrics as 
well. Right ?

> [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: 0001-YARN-5561.YARN-5355.patch, YARN-5561.02.patch, 
> YARN-5561.03.patch, 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

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