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

Posted to yarn-issues@hadoop.apache.org by "Hong Zhiguo (JIRA)" <ji...@apache.org> on 2015/07/31 04:10:04 UTC

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

Hong Zhiguo created YARN-4001:
---------------------------------

             Summary: 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)