[
https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380810#comment-14380810
]
Zhijie Shen commented on YARN-3044:
-----------------------------------
My 2 cents: as to a container, both RM and NM maintain the lifecycle, but they
look at the container from different aspects. To me, RM's container lifecycle
sounds more resource management oriented, while NM's container lifecycle sounds
more container execution oriented. I'm not sure which one is more important to
users.
As to recording all states as well as the events of state transition, we
previously only record a few events more or less because the storage
scalability consideration. Moreover, we only record the information that is
merely enough for YTS web UI/REST web services/CLI to show what is equivalent
to RM shows before for running app.
My suggestion is that we start with reimplementing what we provided in YTS v1,
and add more timeline data on demand later.
> [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)
