[
https://issues.apache.org/jira/browse/YARN-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037341#comment-16037341
]
Jian He commented on YARN-6511:
-------------------------------
thanks [~botong], not sure I'm reading it right:
Looks like for each allocate call, it always does registration for all the
sub-clusters by spinning off #clusters threads and register, will this be a
bottleneck as the allocate is a fairly frequent call. Also, what happens to
the failed-to-register cluster? will it continuously register for each allocate
?
nit: Unused param 'appContext' in splitResourceRequests
> Federation Intercepting and propagating AM-RM communications (part two:
> secondary subclusters added)
> ----------------------------------------------------------------------------------------------------
>
> Key: YARN-6511
> URL: https://issues.apache.org/jira/browse/YARN-6511
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Botong Huang
> Assignee: Botong Huang
> Attachments: YARN-6511-YARN-2915.v1.patch,
> YARN-6511-YARN-2915.v2.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 two jira, which adds secondary subclusters and do full
> split-merge for requests. Part one is in YARN-3666
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
