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

Íñigo Goiri reassigned YARN-10210:
----------------------------------

                  Key: YARN-10210  (was: HADOOP-16543)
    Affects Version/s:     (was: 3.1.2)
                       3.1.2
             Assignee:     (was: Roger Liu)
           Issue Type: Improvement  (was: Bug)
              Project: Hadoop YARN  (was: Hadoop Common)

> Cached DNS name resolution error
> --------------------------------
>
>                 Key: YARN-10210
>                 URL: https://issues.apache.org/jira/browse/YARN-10210
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 3.1.2
>            Reporter: Roger Liu
>            Priority: Major
>
> In Kubernetes, the a node may go down and then come back later with a 
> different IP address. Yarn clients which are already running will be unable 
> to rediscover the node after it comes back up due to caching the original IP 
> address. This is problematic for cases such as Spark HA on Kubernetes, as the 
> node containing the resource manager may go down and come back up, meaning 
> existing node managers must then also be restarted.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to