[
https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650231#comment-14650231
]
Naganarasimha G R commented on YARN-3045:
-----------------------------------------
[~sjlee0], Thanks for the detailed explanation now i am clear about the plans
for TimelineClient and indirect support of flush for it.
bq. If these events are already associated with containers any way, they are
not an issue, right?
Well [~djp] had pointed for 2 new stuff as part of this jira(apart from the
existing container life cycle events), one was NM side application events and
other was container resource localization events. In the later case again
(similar to NM Side Application event) multiple resource paths can be localized
for a given container, so different states of localization cannot be directly
put as event ID's as we need to also publish the information of which resource
this event belongs too.
hence had suggested earlier as :
??For Localization i feel it can be under ContainerEntity and the EventID can
have Event Type (REQUEST,LOCALIZED,LOCALIZATION_FAILED)and PATH of the
localized resource.??
> [Event producers] Implement NM writing container lifecycle events to ATS
> ------------------------------------------------------------------------
>
> Key: YARN-3045
> URL: https://issues.apache.org/jira/browse/YARN-3045
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Naganarasimha G R
> Attachments: YARN-3045-YARN-2928.002.patch,
> YARN-3045-YARN-2928.003.patch, YARN-3045-YARN-2928.004.patch,
> YARN-3045-YARN-2928.005.patch, YARN-3045-YARN-2928.006.patch,
> YARN-3045.20150420-1.patch
>
>
> Per design in YARN-2928, implement NM writing container lifecycle events and
> container system metrics to ATS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
