[
https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520929#comment-14520929
]
Vinod Kumar Vavilapalli commented on YARN-3045:
-----------------------------------------------
bq. IIUC from discussions in 3044, as suggested by Junping Du we have container
metrics published as optional feature in RM side and have also coded
accordingly, and even Sangjin Lee recent comment was inline with this idea.
Hence earlier added some code in NM side to get all the required information
about container which are currently got it in RM.
Good to know. Will look at that JIRA. My point is we need to do it only in one
place, either RM or NM. On first reaction, writing from NMs is more
distributed, but we'll see.
bq. Gather all timeline publishing code in one place and have a single async
dispatcher taking caring of publishing timeline entities/events.
I am inclined towards this approach. Kind of similar to what happens in
MapReduce AM. There is no point in spraying TimelineClient all over the NM?
> [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.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)
