[
https://issues.apache.org/jira/browse/YARN-11122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-11122:
------------------------------
Target Version/s: 3.4.0 (was: 3.3.0, 3.3.1, 3.3.2)
> Support getClusterNodes API in FederationClientInterceptor
> ----------------------------------------------------------
>
> Key: YARN-11122
> URL: https://issues.apache.org/jira/browse/YARN-11122
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: federation
> Affects Versions: 3.3.0, 3.3.1, 3.3.2
> Reporter: Shilun Fan
> Assignee: Shilun Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Original Estimate: 48h
> Time Spent: 2h 10m
> Remaining Estimate: 45h 50m
>
> Yarn Federation is a very useful feature, especially important in clusters
> with more than 1,000 units. For example, we have 2 offline clusters, which
> are used for ad-hoc and offline scheduling (etl) respectively. We hope to be
> able to isolate and rationally use 2 The resources of a cluster, at night,
> adhoc resources can be used by the etl cluster; at the same time, during
> breakfast (9:00-22:00), the etl cluster resources can also be used by the
> adhoc cluster.
> At the same time, so that more people can use this feature, gradually improve
> the method that has not been implemented.
> In YARN-10465, some methods have been implemented, from a personal point of
> view, some doubts.
> Question 1: Without considering the metric implementation, it is impossible
> to understand the execution of related functions.
> Question 2: Using multi-threading and reflection implementation, the
> readability of the related logic is relatively poor, and there is not much
> performance difference between this method and the conventional loop method
> to obtain the theory.
> Question 3: The code is already 2 years old, merged into the local branch,
> there may be conflicts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
