[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666119#action_12666119
]
Steve Loughran commented on HADOOP-5083:
----------------------------------------
# Obviously, I'd like to see the new code integrated with HADOOP-3628. Could
you use method names and a stub lifecycle that is compatible?
# the JobTracker should not be the place that starts an external JVM, as there
are JVM options, console logs and other lifecycle issues to consider -such as
keeping the JobHistory daemon live while the JobTracker restarts, yet still
being able to log and terminate the JobHistory daemon when required.
# This is a really good opportunity to start HtmlUnit tests for the JSP pages,
especially considering the amount of Java code embedded into them.
> 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
> 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.
