[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665895#action_12665895
]
Doug Cutting commented on HADOOP-5083:
--------------------------------------
By default we might continue to run this service in the same JVM as the
jobtracker, so we don't force the maintenance of another daemon on every
installation. Only folks who have huge clusters need configure things so that
this is run as a separate process, potentially on a separate host. So
JobTracker.main() can check the configuration to see if it should, in addition
to starting the jobtracker, start the job history service. In both cases, it
should use independent ports from the jobtracker.
In general, it should be simple to run all of our daemons in a single JVM, or
to mix-and-match them. This should require at most a custom main() routine per
JVM. We use this kind of configuration for unit testing already.
> 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
>
> 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.
