[
https://issues.apache.org/jira/browse/YARN-11391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644916#comment-17644916
]
ASF GitHub Bot commented on YARN-11391:
---------------------------------------
lnbest0707 commented on PR #5196:
URL: https://github.com/apache/hadoop/pull/5196#issuecomment-1343068816
@slfan1989 thanks a lot for your review. Will add the instructions, do you
have any suggestions where to add it? Just in the commit message or in a
separate file (or which file).
Besides, I feel the
[issue](https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5196/2/artifact/out/new-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.html)
reported by Jenkins a false alert. The "Unsynchronized access" reported by it
is a READ call from a log function. I don't think we should add any locks on
logging call. Please share any suggestions to bypass it. Thanks.
> 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]
