-
Notifications
You must be signed in to change notification settings - Fork 9.2k
Yarn 11391 #5277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Yarn 11391 #5277
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
💔 -1 overall
This message was automatically generated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
The patch reuses the resolver introduced from the HDFS side and apply similar logic to YARN RM service addresses resolving.
To utilize the YARN DNS support and use DNS as endpoint, simply upgrade the hadoop binary and revise configs from, for example:
yarn.resourcemanager.address.rm1 rm1_address:8032 yarn.resourcemanager.scheduler.address.rm1 rm1_address:8030 yarn.resourcemanager.resource-tracker.address.rm1 rm1_address:8031 yarn.resourcemanager.admin.address.rm1 rm1_address:8033 yarn.resourcemanager.webapp.address.rm1 rm1_address:8088 yarn.resourcemanager.webapp.https.address.rm1 rm1_address:8090 yarn.resourcemanager.address.rm2 rm2_address:8032 yarn.resourcemanager.scheduler.address.rm2 rm2_address:8030 yarn.resourcemanager.resource-tracker.address.rm2 rm2_address:8031 yarn.resourcemanager.admin.address.rm2 rm2_address:8033 yarn.resourcemanager.webapp.address.rm2 rm2_address:8088 yarn.resourcemanager.webapp.https.address.rm2 rm2_address:8090 yarn.resourcemanager.ha.rm-ids rm1,rm2 to: yarn.resourcemanager.address.rm1 rm_multi_a_dns:8032 yarn.resourcemanager.scheduler.address.rm1 rm_multi_a_dns:8030 yarn.resourcemanager.resource-tracker.address.rm1 rm_multi_a_dns:8031 yarn.resourcemanager.admin.address.rm1 rm_multi_a_dns:8033 yarn.resourcemanager.webapp.address.rm1 rm_multi_a_dns:8088 yarn.resourcemanager.webapp.https.address.rm1 rm_multi_a_dns:8090 yarn.resourcemanager.ha.rm-ids rm1 yarn.resourcemanager.ha.resolve-needed true yarn.resourcemanager.ha.resolver.useFQDN true # required in secure mode yarn.resourcemanager.ha.refresh-period-ms 180000 # 3 minwhere rm_multi_a_dns is a multi-A DNS record for rm1_address and rm2_address. This means the following output on the terminal.
$ dig +short <rm_multi_a_dns> | xargs -n +1 dig +short -x | sort
<rm1_address>
<rm2_address>
For the newly introduced flags, please refer to yarn-default.xml.
How was this patch tested?
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?