[
https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523390#comment-14523390
]
Naganarasimha G R commented on YARN-3044:
-----------------------------------------
Hi [~vinodkv],
bq. But it's really about potential loss of information in many not-so rare
cases like when container gets allocated but gets preempted or released by AM
before it really starts.
Yes it would be good to capture all these information but initialy to start of
with it was discussed earlier that we will start of with basic life cycle
events and for others we can add on subsequently. In those special cases you
mentioned my opinion is we can try to publish from RM
bq. We can just tunnel some of the RM-originated information through AMs to the
NM.
Did not quite get this clearly, can we enforce RM originated entities/events to
be published by client's AM ?
bq. container's life-cycle ends either on the RM or the AM. We can take a dual
pronged approach here.
Well i am not sure we can enforce container's life-cycle ending in AM to be
published to ATS. but anyway RM will get informed by container liveliness
monitor if the container's life-cycle ends in AM right ?
bq. We can take a dual pronged approach here? That or we make the RM-publisher
itself a distributed push.
IMO dual pronged approach would be better, we can rely on NMs to post normal
life cycle events and in rare cases where NM cant handle, RM publish events
directly to ATS.
And might be distributed push might not work as in the cases which you
mentioned NM might not be able to handle publishing as TimelineCollector might
not be created yet.
> [Event producers] Implement RM writing app lifecycle events to ATS
> ------------------------------------------------------------------
>
> Key: YARN-3044
> URL: https://issues.apache.org/jira/browse/YARN-3044
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Naganarasimha G R
> Attachments: YARN-3044-YARN-2928.004.patch,
> YARN-3044.20150325-1.patch, YARN-3044.20150406-1.patch,
> YARN-3044.20150416-1.patch
>
>
> Per design in YARN-2928, implement RM writing app lifecycle events to ATS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
