[
https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699645#comment-14699645
]
Allan Wilson commented on YARN-4024:
------------------------------------
When a nodemanager is decommissioned, is the IP cached for that host flushed
out of the cache? Normally when a host gets a new IP its because it gets moved
or some other deliberate maintenance which would normally be preceded by a
decommission. If the IP is flushed when decommissioned or a IP is always
resolved from the host name when a new or recommissioned nodemanager is added
to the cluster I think that would be adequate IMHO.
Also, it may be worthwhile or adequate to expose the method in a yarn rmadin
command to force a flush of the IP cache. Is this IP cache the same used for
Rack Awareness by the RM?
Thanks
> YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat
> ----------------------------------------------------------------------
>
> Key: YARN-4024
> URL: https://issues.apache.org/jira/browse/YARN-4024
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Wangda Tan
> Assignee: Hong Zhiguo
> Attachments: YARN-4024-draft.patch
>
>
> Currently, YARN RM NodesListManager will resolve IP address every time when
> node doing heartbeat. When DNS server becomes slow, NM heartbeat will be
> blocked and cannot make progress.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
