[ 
https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301543#comment-14301543
 ] 

Sangjin Lee commented on YARN-3045:
-----------------------------------

In this case, NM would act as a timeline service client, not as a direct 
aggregator/writer to the backing storage.

The idea is for the NM to find the right timeline aggregator, and invoke the 
timeline service client API to send the timeline events/metrics to that 
aggregator. That's why the service discovery feature (YARN-3039) is needed for 
this.

Does it help clarify it?

> implement NM writing container lifecycle events and container system metrics 
> 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
>
> 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)

Reply via email to