[ 
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohith Sharma K S updated YARN-5699:
------------------------------------
    Attachment: 0001-YARN-5699.patch

Updated the patch with following changes.
Application : 
# YARN_APPLICATION_FINISHED event has some app level information, I have moved 
to entity level info.

ApplicationAttempt :
# Events YARN_APPLICATION_ATTEMPT_FINISHED and 
YARN_APPLICATION_ATTEMPT_REGISTERED has application report specific info 
details. These have been moved to entity info level.

Container : 
# Events YARN_RM_CONTAINER_CREATED and YARN_RM_CONTAINER_FINISHED had container 
report specific info details. These have been moved to entity info level.
# Remove duplicated information which was published from NM publisher info.
# Added container created and container finished information in entity level 
info.

> 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
>         Attachments: 0001-YARN-5699.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

Reply via email to