[
https://issues.apache.org/jira/browse/HADOOP-16543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937082#comment-16937082
]
Fengnan Li commented on HADOOP-16543:
-------------------------------------
[~elgoiri] Sorry for coming back late. Right now we use DNS only in
ResourceManager for router so we haven't run into this issue in production yet.
But the general issue of DNS caching still exists. A sort of mitigation of our
current strategy is to give each host a DNS alias instead of using its host
directly and this at least get rid of host replacement part.
> Cached DNS name resolution error
> --------------------------------
>
> Key: HADOOP-16543
> URL: https://issues.apache.org/jira/browse/HADOOP-16543
> Project: Hadoop Common
> Issue Type: Bug
> 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: [email protected]
For additional commands, e-mail: [email protected]
