hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Botong Huang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3666) Federation Intercepting and propagating AM-RM communications (part one: home RM only)
Date Tue, 30 May 2017 21:05:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Botong Huang updated YARN-3666:
    Attachment: YARN-3666-YARN-2915.v8.patch

v8: comments addressed and rebased after Yarn-6666

> Federation Intercepting and propagating AM-RM communications (part one: home RM only)
> -------------------------------------------------------------------------------------
>                 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
>         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
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message