[jira] [Commented] (YARN-11391) Support using DNS to resolve yarn services to IP addresses

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-11391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644545#comment-17644545 ] 

ASF GitHub Bot commented on YARN-11391:
---------------------------------------

lnbest0707 opened a new pull request, #5196:
URL: https://github.com/apache/hadoop/pull/5196

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   Add DNS discovery support for YARN RM services. It would accept DNS multi-A record as input from yarn-site.xml. Upon configurations, it would resolve the DNS and do reverse lookup. Both server (RM, NM, app container) and client could utilize the same DNS functionality. Besides, it is backward compatible with plain DNS A record.
   
   ### How was this patch tested?
   local mvn test
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files?
   
   




> 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
>
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org