[
https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382387#comment-14382387
]
Junping Du commented on YARN-3044:
----------------------------------
Thanks guys for good discussions above especially for topic of posting app
lifecycle events from NM or RM. Can I propose that we do both ways in
development stage?
I fully understand the concern from [~sjlee0] that RM may not afford tens of
thousands containers in large size cluster. However, we can disable RM-side
posting work in production environment by default. We can have different entity
types, e.g. NM_CONTAINER_EVENT, RM_CONTAINER_EVENT, for containers' event get
posted from NM or RM then we can fully understand how the world could be
different from NM and RM (i.e. start time, end time, etc.). It not only benefit
the development cycle, but also benefit the trouble-shooting work in a
production environment as this apple-to-apple comparing may provide some hints
to user. Given this (both way) doesn't sounds like too much work, I think it
may worth to do. Thoughts?
> [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.20150325-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)
