hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6064) Bad links to jobhistory server
Date Wed, 03 Sep 2014 00:27:52 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119051#comment-14119051
] 

Karthik Kambatla commented on MAPREDUCE-6064:
---------------------------------------------

It might be reasonable to not have a default value for JHS node. If nothing is specified,
use the RM's node name/ip with the default port. 

> 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)

Mime
View raw message