[ https://issues.apache.org/jira/browse/YARN-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621323#comment-13621323 ]
Hudson commented on YARN-538: ----------------------------- Integrated in Hadoop-trunk-Commit #3555 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3555/]) YARN-538. RM address DNS lookup can cause unnecessary slowness on every JHS page load. (sandyr via tucu) (Revision 1464197) Result = SUCCESS tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464197 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java > RM address DNS lookup can cause unnecessary slowness on every JHS page load > ---------------------------------------------------------------------------- > > Key: YARN-538 > URL: https://issues.apache.org/jira/browse/YARN-538 > Project: Hadoop YARN > Issue Type: Improvement > Affects Versions: 2.0.3-alpha > Reporter: Sandy Ryza > Assignee: Sandy Ryza > Fix For: 2.0.5-beta > > Attachments: MAPREDUCE-5111.patch > > > When I run the job history server locally, every page load takes in the 10s > of seconds. I profiled the process and discovered that all the extra time > was spent inside YarnConfiguration#getRMWebAppURL, trying to resolve 0.0.0.0 > to a hostname. When I changed my yarn.resourcemanager.address to localhost, > the page load times decreased drastically. > There's no that we need to perform this resolution on every page load. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira