[jira] [Commented] (MAPREDUCE-5111) RM address DNS lookup can cause unnecessary slowness on every JHS page load
[ https://issues.apache.org/jira/browse/MAPREDUCE-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621296#comment-13621296 ] Alejandro Abdelnur commented on MAPREDUCE-5111: --- +1 RM address DNS lookup can cause unnecessary slowness on every JHS page load Key: MAPREDUCE-5111 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5111 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver Affects Versions: 2.0.3-alpha Reporter: Sandy Ryza Assignee: Sandy Ryza 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
[jira] [Commented] (MAPREDUCE-5111) RM address DNS lookup can cause unnecessary slowness on every JHS page load
[ https://issues.apache.org/jira/browse/MAPREDUCE-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620424#comment-13620424 ] Sandy Ryza commented on MAPREDUCE-5111: --- Attached patch uses modifies YarnConfiguration#getRMWebAppHostAndPort to use NetUtils#getConnectAddress, which avoids trying to resolve the 0.0.0.0. Verified on a pseudo-distributed cluster that the patch fixes the page load slowness. RM address DNS lookup can cause unnecessary slowness on every JHS page load Key: MAPREDUCE-5111 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5111 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobhistoryserver Affects Versions: 2.0.3-alpha Reporter: Sandy Ryza Assignee: Sandy Ryza 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
[jira] [Commented] (MAPREDUCE-5111) RM address DNS lookup can cause unnecessary slowness on every JHS page load
[
https://issues.apache.org/jira/browse/MAPREDUCE-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620441#comment-13620441
]
Hadoop QA commented on MAPREDUCE-5111:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576692/MAPREDUCE-5111.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3492//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3492//console
This message is automatically generated.
RM address DNS lookup can cause unnecessary slowness on every JHS page load
Key: MAPREDUCE-5111
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5111
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
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
