[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666226#action_12666226
]
Arun C Murthy commented on HADOOP-5083:
---------------------------------------
bq. So JobTracker.main() can check the configuration to see if it should, in
addition to starting the jobtracker, start the job history service.
Doug, I agree with the overall direction of your proposal.
However, it seems to me that you do not want the JobTracker starting the
stand-alone JobHistoryServer, rather we should get the
$ bin/hadoop jobtracker
command to start the job-history server which can then be managed (e.g. restart
on failure) after by daemontools (http://cr.yp.to/daemontools.html) or init.d
or some such. It's reasonably safe to restart the job-history server since it's
stateless and read-only. Thoughts?
> 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.
