[
https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380675#comment-14380675
]
Vrushali C commented on YARN-3044:
----------------------------------
bq. Well i too had the same doubt whether we need to capture very minute part
of the life cycle events as present in the RMAppState(/YarnApplicationState)
and RMAppAttemptState. That is the reason i had posted earlier but Sangjin Lee
had opined to start of with the basic ones hence provided this patch. Based on
the input from all will add other required states
What is the reasoning behind capturing some but not all application lifecycle
state changes? I believe we should not be selectively filtering out capturing
of application lifecycle state changes in the next gen timeline service.
> [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)
