[
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546344#comment-15546344
]
Li Lu commented on YARN-5699:
-----------------------------
I think the major concern is that when putting useful fields into event info
field instead of entity info field, we lost the ability to easily query them.
For example, if an user would like to list all containers with a specific exit
code, or finished within a time window. This said, I think the key point is to
put data related to the whole entity into the entity's info field. Ideally we
should only put some quite lightweight data into the event's info fields (since
they're not easily to query), but if we share a lot of code path we may want to
either replicate those data in entity info, or refactor the code?
> 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
