[
https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040075#comment-16040075
]
Hong Zhiguo edited comment on YARN-4024 at 6/7/17 3:23 AM:
-----------------------------------------------------------
[~maobaolong], we don't turn on log-aggregation to avoid the pressure to
network and HDFS.
For the code you questioned, when the node status is changed, we MUST invalid
corresponding cache item which is learned when the node is in another state,
because the IP address may be changed besides status changing.
I think it's OK to add a break statement in "default" case, and it's also OK to
invalidate the cache item when we get an wrong event.
was (Author: zhiguohong):
[~maobaolong], we don't turn on log-aggregation to avoid the pressure to
network and HDFS.
> 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
> Components: resourcemanager
> Reporter: Wangda Tan
> Assignee: Hong Zhiguo
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: YARN-4024-draft.patch, YARN-4024-draft-v2.patch,
> YARN-4024-draft-v3.patch, YARN-4024-v4.patch, YARN-4024-v5.patch,
> YARN-4024-v6.patch, YARN-4024-v7.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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
