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

Zhijie Shen commented on YARN-3039:
-----------------------------------

bq. The RM will likely not use the service discovery. For example, for RM to 
write the app started event, the timeline aggregator may not even be 
initialized yet.

I think so, too. RM has its own builtin aggregator, and RM directly writes 
through it. 

Thanks for the patch, Junping! One suggestion: in the heartbeat, instead of 
always sending the snapshot of the aggregator address info, can we send the 
incremental information upon any change happens to the aggregator address 
table. Usually, the aggregator will not change it place often, such that we can 
avoid unnecessary additional traffic in most heartbeats.

> [Aggregator wireup] Implement ATS writer service discovery
> ----------------------------------------------------------
>
>                 Key: YARN-3039
>                 URL: https://issues.apache.org/jira/browse/YARN-3039
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Junping Du
>         Attachments: Service Binding for applicationaggregator of ATS 
> (draft).pdf, YARN-3039-no-test.patch
>
>
> Per design in YARN-2928, implement ATS writer service discovery. This is 
> essential for off-node clients to send writes to the right ATS writer. This 
> should also handle the case of AM failures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to