Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.3-alpha
-
None
-
None
-
Reviewed
Description
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.