[
https://issues.apache.org/jira/browse/MAPREDUCE-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla moved YARN-2490 to MAPREDUCE-6064:
---------------------------------------------------
Key: MAPREDUCE-6064 (was: YARN-2490)
Project: Hadoop Map/Reduce (was: Hadoop YARN)
> Bad links to jobhistory server
> ------------------------------
>
> Key: MAPREDUCE-6064
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6064
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Todd Lipcon
>
> If you run an MR/YARN cluster without configuring the jobhistory URL, you get
> some really bad usability:
> - your jobs still produce JobHistory links
> - the job history link goes to whichever NM the AM happened to run on
> Even if you run the job history server on the same server as the RM, your
> links will be incorrect unless you've explicitly configured its hostname.
> If JobHistory isn't running, we shouldn't produce URLs (or we should by
> default embed JobHistory inside the RM). If we require a hostname beyond
> 0.0.0.0, we should refuse to start the JH server with 0.0.0.0 as its
> configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
