hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery
Date Mon, 16 Mar 2015 20:08:40 GMT

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

Sangjin Lee commented on YARN-3039:
-----------------------------------

[~zjshen],

{quote}
So in this work, since we have involved the rpc call, I raise the thought of using the rpc
call to start app-level aggregator instead of aux service lifecycle event handler. IMHO, it's
necessary in the future when the aggregator no longer resides in the same process of NM, such
that I can see the merit of uniforming the way to start app-level aggregator.
{quote}

I completely agree that we need an RPC-based mechanism to create and shut down the app-level
aggregator/collector. As [~djp] mentioned, that work can be covered in making the per-node
aggregator/collector a standalone daemon.

> [Aggregator wireup] Implement ATS app-appgregator 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, Service
Discovery For Application Aggregator of ATS (v2).pdf, YARN-3039-no-test.patch, YARN-3039-v2-incomplete.patch,
YARN-3039-v3-core-changes-only.patch, YARN-3039-v4.patch, YARN-3039-v5.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)

Mime
View raw message