[
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: 0002-YARN-5699.patch
Updating the patch with following changes. Patch is rebased against trunk as
this need to commit in trunk.
# Added container finish time to get published on container finish event.
container create time is not added, user can take this time from entity created
time itself.
# appUpdated event publish kept unmodified as per review comment.
# Removed duplicated information getting published during attempt start and
attempt end time as per Varun's review comment.
# tracking URL and original trackingURL published in entity info level.
Original tracking URL life time is same as application run time. When
application is running, client need to construct URL with proxy/without proxy
as it is done for rendering AppsBlock.
# At last, all the constants are renamed to *_INFO rather than *_EVENT_INFO or
*_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, 0002-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: [email protected]
For additional commands, e-mail: [email protected]
