Sangjin Lee commented on YARN-5699:

The created time just seems redundant. Is there something that cannot be done 
by the explicit created time attribute? Rohith said

bq. It is only for easier accessibility rather than going through event time 

We're already setting it to the entity created time, so you would *not* be 
going through event time stamps for the created time. So I'm not sure whether 
we need to store it again as part of the entity info.

> 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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to