You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Botong Huang (JIRA)" <ji...@apache.org> on 2017/05/31 20:48:04 UTC
[jira] [Commented] (YARN-3666) Federation Intercepting and
propagating AM- home RM communications
[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031930#comment-16031930 ]
Botong Huang commented on YARN-3666:
------------------------------------
Great, thanks [~subru] and [~curino] for the feedback!
@All Let's move on to Federation interceptor part 2 in YARN-6511.
> Federation Intercepting and propagating AM- home RM communications
> ------------------------------------------------------------------
>
> Key: YARN-3666
> URL: https://issues.apache.org/jira/browse/YARN-3666
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Kishore Chaliparambil
> Assignee: Botong Huang
> Fix For: YARN-2915
>
> Attachments: YARN-3666-YARN-2915.v1.patch, YARN-3666-YARN-2915.v2.patch, YARN-3666-YARN-2915.v3.patch, YARN-3666-YARN-2915.v4.patch, YARN-3666-YARN-2915.v5.patch, YARN-3666-YARN-2915.v6.patch, YARN-3666-YARN-2915.v7.patch, YARN-3666-YARN-2915.v8.patch, YARN-3666-YARN-2915.v9.patch
>
>
> In order, to support transparent "spanning" of jobs across sub-clusters, all AM-RM communications are proxied (via YARN-2884).
> This JIRA tracks federation-specific mechanisms that decide how to "split/broadcast" requests to the RMs and "merge" answers to
> the AM.
> This the part one jira, which sets up the basic structure, without secondary subclusters. All requests are forwarded to home subcluster. Part two is in YARN-6511
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org