[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

["Junping Du (JIRA)" <ji...@apache.org>]

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

Junping Du commented on YARN-3039:
----------------------------------

Hi [~rkanter], thanks for sharing your thoughts here. 
I think as a generic, external service for YARN, YARN-913 may not meet our particular requirements here, like: 
- timeline service will serve as build-in service, not necessary for application to register service explicitly
- NM also need this aggregators info to aggregate info related to containers running on top of it.
- We have preference to bind service to local node of AM container
- Now, the launching of NM aggregators is not in way of YARN service container (see YARN-3033)
Also, I think we may not want this built-in service (as a standalone feature) to depends on another big feature in progress when unnecessary. Thoughts?

> [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: Robert Kanter
>
> 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)