[
https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029974#comment-16029974
]
Botong Huang commented on YARN-3666:
------------------------------------
I've just opened YARN-6666 for this failure:
org.apache.hadoop.yarn.server.router.clientrm.TestRouterClientRMServicetestRouterClientRMServiceE2E
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
