[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666242#action_12666242
]
Doug Cutting commented on HADOOP-5083:
--------------------------------------
> you do not want the JobTracker starting the stand-alone JobHistoryServer
When it's standalone, then it should certainly be started separately. But I
think, for simplicity and back-compatibility, the default behavior might be for
it to continue to run within the JobTracker JVM. We can add a main() routine,
command line commands, etc. to run it separately and a config option to stop it
from being run within the JobTracker JVM.
> 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.
