You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/03/28 03:31:15 UTC
[jira] [Updated] (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:all-tabpanel ]
Sandy Ryza updated MAPREDUCE-5111:
----------------------------------
Summary: RM address DNS lookup can cause unnecessary slowness on every JHS page load (was: Unnecessary RM address DNS lookup can cause unnecessary slowness on every JHS page load )
> 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
>
> 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