hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory
Date Tue, 10 Feb 2009 06:48:59 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Amar Kamat updated HADOOP-5083:

    Attachment: HADOOP-5083-v1.11.4.patch

Attaching a patch that address Sharad's comments. Moved all the JobHistory related code to
JobHistroyServer. JobHistoryServer now also acts as JobHistory info manager. Result of _test-patch_
is as follows
-1 overall.
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 17 new or modified tests.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     -1 findbugs.  The patch appears to introduce 3 new Findbugs warnings.
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec]     -1 release audit.  The applied patch generated 835 release audit warnings
(more than the trunk's current 832 warnings).

The findbugs warning is because of
-  {{System.exit()}} 
- {{Thread.sleep()}} with lock : This is also required as even while sleeping the lock cant
be released. The locks is taken while initializing and the lock ideally should not be released
until the init completes.

The release aduit warning is for the jsp files. They were simply moved from one folder to
another. Also previously these files were not having any headers.

> 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.2.patch, HADOOP-5083-v1.9.4.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.

View raw message