[
https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570985#comment-15570985
]
Rohith Sharma K S commented on YARN-5561:
-----------------------------------------
Thanks for clarifications..
Though utility class is very useful for converting reports, one major concern
is number of REST calls to be invoked by user. Especially in Web, this will
become 2 REST calls which decrease the performance.
Basically, me and Li lu was thinking to embedded
TimelineYARNEntityReaderWebService to timelinereader daemon with REST path
*/ws/v2/applicationhistory*. These REST end points would take care of
retrieving entities from storage and convert to required YARN reports such as
ApplicationAttemptReport or ContainerReport etc.
bq. Also, please note that what's contained in the current REST output would
likely to be a superset of *Report;
I agree that current *Report would be subset of TimelineEntity object. So ,
this we can solve by defining new *Report which compatible with ATSv2 either by
extending current *reports since metrics are required. If any new fields
published to ATS, then It is contract between publisher and reader that these
information fields should added in *Report. New *report class is only wrapper
over TimelineRntity object for YARN entities. And at any point of time, if user
thinks he need more informations, he can query from ATSv2 which is always open.
> [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
(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
