[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568675#comment-15568675
]
Rohith Sharma K S commented on YARN-5699:
-----------------------------------------
bq. Created time is at the topmost level in an entity. We don't need to go
through event timestamps for it.
What about end time? End time has to be get from event time stamp. But anyway,
I have added a
[comment|https://issues.apache.org/jira/browse/YARN-5561?focusedCommentId=15568429&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15568429]
for streamlining YARN entities publishing, I think we should decide for
providing YARN entities converter rather than fixing individual many bugs.
> Retrospect yarn 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
> Attachments: 0001-YARN-5699.YARN-5355.patch, 0001-YARN-5699.patch,
> 0002-YARN-5699.YARN-5355.patch
>
>
> 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
