[
https://issues.apache.org/jira/browse/YARN-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783093#comment-16783093
]
Hudson commented on YARN-9332:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16113 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16113/])
YARN-9332. RackResolver tool should accept multiple hosts. Contributed
(aajisaka: rev e20b5ef52cbc4f9f3bd6cdc36cb359eece63bfbc)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/RackResolver.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestRackResolver.java
> RackResolver tool should accept multiple hosts
> ----------------------------------------------
>
> Key: YARN-9332
> URL: https://issues.apache.org/jira/browse/YARN-9332
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
> Affects Versions: 2.9.2, 3.0.3, 2.8.5, 2.7.7, 3.1.2
> Reporter: Lantao Jin
> Assignee: Lantao Jin
> Priority: Minor
> Fix For: 3.3.0, 3.2.1
>
> Attachments: YARN-9332.001.patch, YARN-9332.002.patch,
> YARN-9332.003.patch
>
>
> RackResolver as a public rack resolver tool only offers a method {{public
> static Node resolve(String hostName)}} which only accepts one host a time.
> Actually the internal implementation class {{DNSToSwitchMapping}} always
> accept a host list as its input and return a list of resolved racks. That's
> cause the invoker like Spark takes a long time to resolve the rack info when
> handling abundant tasks (a mass of loops to execute script to resolve rack
> info).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
