[
https://issues.apache.org/jira/browse/YARN-11391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644556#comment-17644556
]
ASF GitHub Bot commented on YARN-11391:
---------------------------------------
lnbest0707 commented on PR #5196:
URL: https://github.com/apache/hadoop/pull/5196#issuecomment-1341791934
Hi @slfan1989 thanks for your reply.
> I think it would be better to make this part an optional configuration.
None DNS resolving logics would be triggered if
"yarn.resourcemanager.ha.resolve-needed" set as false (which is its default
value).
> Why the code submission is 2 different users?
May I know where there are two people in code commits? The other name is the
key name for my github access token.
> Support using DNS to resolve yarn services to IP addresses
> ----------------------------------------------------------
>
> Key: YARN-11391
> URL: https://issues.apache.org/jira/browse/YARN-11391
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Shuyi Zhang
> Priority: Major
> Labels: pull-request-available
>
> We have been using A-record (hostname) for discovering YARN control
> planes(RM, JHS) from both the server and client sides. The components
> discover each other using hostnames (DNS A-records) which are preconfigured
> in YARN configurations (mapred-site.xml and yarn-site.xml). However, the
> hard-coded address mapping is prohibitive to perform appropriate failure
> recovery and node replacement. Any host replacement, adding, or removing
> requires client integration, which is a quite painful process.
> It is essential to find a solution where the discovery configuration of
> different components in the cluster stays intact and is able to resolve with
> the latest hostname/records.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
