[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548475#comment-15548475
]
Varun Saxena commented on YARN-5699:
------------------------------------
bq. For containers, some of the event info should be published at container
info level.
Agree with the intention behind this JIRA [~rohithsharma] . Some info which we
may have to query and does not change per event i.e. this info is not repeated
across events, we should have at entity info level.
Only info which is strictly specific to an event is what can be kept at event
info level. This we can keep as the thumb rule for publishing info. However, we
can also consider publishing it at both places on need basis (i.e. if and when
we find a use case).
> 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
