[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666250#action_12666250
]
Doug Cutting commented on HADOOP-5083:
--------------------------------------
> This is what the attached patch does. Review?
The patch looks generally good to me. The change to
conf/hadoop-site.xml.template seems accidental. I think we should not default
mapred.job.history.http.address to 0.0.0.0:50040 (as in the patch) but rather
leave it empty, so that job history continues to run in the JobTracker by
default. We should also document that this is what's done if it is empty in
hadoop-default.xml, and change the implementation so that an empty string here
is interpreted as null.
> Optionally a separate daemon should serve JobHistory
> ----------------------------------------------------
>
> Key: HADOOP-5083
> URL: https://issues.apache.org/jira/browse/HADOOP-5083
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Arun C Murthy
> Assignee: Amar Kamat
> Attachments: HADOOP-5083-v1.2.patch
>
>
> Currently the JobTracker serves the JobHistory to end-users off files
> local-disk/hdfs. While running very large clusters with a large user-base
> might result in lots of traffic for job-history which needlessly taxes the
> JobTracker. The proposal is to have an optional daemon which handles serving
> of job-history requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
