[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672901#action_12672901
]
Sharad Agarwal commented on HADOOP-5083:
----------------------------------------
some comments:
JobHistoryServer: do we need Active/Passive state? I think embedded boolean
should be good enough as there are only 2 cases embedded/standalone.
HttpServer: I think adding otherWebAppContext may be avoided. we can use
already available method addContext(Context ctxt, boolean isFiltered). Or
perhaps we just filter out the jobhistory url in case of standalone.
> 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.11.4.patch, HADOOP-5083-v1.11.5.patch,
> 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.
