[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665708#action_12665708
]
Amar Kamat commented on HADOOP-5083:
------------------------------------
bq. Things to ponder :
- What if no _job-history-server_ information is not passed to the jobtracker
i.e is missing?
-# bail out
-# start it from the jobtracker in a separate jvm
-# ignore and continue
-# support it in the jobtracker's webserver as done today
I think (1) will be the simpler but too restrictive, (2) should be fine but
complicated (overhead etc), (3) will be simpler but not user friendly and (4)
should be fine but will be risky
> 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.
