[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670749#action_12670749
]
Sharad Agarwal commented on HADOOP-5083:
----------------------------------------
Some comments on the patch:
I think we should move all history related code from Jobtracker to another
common class which get used from both in process or standalone mode. This class
encapsulates all history related code like whether it is running in local mode
or standalone mode; and let jobtracker just instantiate it.
Also, jsps could be made agnostic that those are running in jobtracker's jvm or
standalone. They just invoke methods on the instance of this common class.
> 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, HADOOP-5083-v1.9.4.patch,
> HADOOP-5083-v1.9.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.
