You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/08/06 20:42:07 UTC

[jira] [Resolved] (YARN-4001) normalizeHostName takes too much of execution time

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

Wangda Tan resolved YARN-4001.
------------------------------
    Resolution: Duplicate

[~zhiguohong], I found this issue after filed YARN-4024, since we have some discussions on YARN-4024 already. I suggest to close this one as duplicated and please feel free to assign YARN-4024 to you.

> normalizeHostName takes too much of execution time
> --------------------------------------------------
>
>                 Key: YARN-4001
>                 URL: https://issues.apache.org/jira/browse/YARN-4001
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>            Reporter: Hong Zhiguo
>            Assignee: Hong Zhiguo
>            Priority: Minor
>
> For each NodeHeartbeatRequest, NetUtils.normalizeHostName is called under a lock.  I did profiling for a very large cluster and found out NetUtils.normalizeHostName takes most execution time of ResourceTrackerService.nodeHeartbeat(...).
> We'd better have an option to use raw IP (plus port) as the Node identity to scale for large clusters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)