[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15551391#comment-15551391
]
Rohith Sharma K S commented on YARN-5699:
-----------------------------------------
I think this is the time to decide should we support translation layer for YARN
entities to get attempts-report, container-reports, application-report. It can
be additional web service in ATS2 similar to */ws/v1/applicationhistory*.
Major concern of this JIRA is about deserializing attempt-report and
container-report for Web UI. If we get much easier translation layer from java,
it would be much easier. Other wise, it is tedious task for deserializing
entity payload if any change in the publishing entity.
> Retrospect container entity fields which are publishing in events info fields.
> ------------------------------------------------------------------------------
>
> Key: YARN-5699
> URL: https://issues.apache.org/jira/browse/YARN-5699
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
>
> Currently, all the container information are published at 2 places. Some of
> them are at entity info(top-level) and some are at event info.
> For containers, some of the event info should be published at container info
> level. For example : container exist status, container state, createdTime,
> finished time. These are general information to container required for
> container-report. So it is better to publish at top level info field.
--
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
