You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/12/07 22:56:00 UTC

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

     [ https://issues.apache.org/jira/browse/YARN-11391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated YARN-11391:
----------------------------------
    Labels: pull-request-available  (was: )

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