Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 59593 invoked from network); 10 Feb 2009 06:49:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Feb 2009 06:49:25 -0000 Received: (qmail 73387 invoked by uid 500); 10 Feb 2009 06:49:22 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 73344 invoked by uid 500); 10 Feb 2009 06:49:22 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 73333 invoked by uid 99); 10 Feb 2009 06:49:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2009 22:49:22 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2009 06:49:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AC463234C4B3 for ; Mon, 9 Feb 2009 22:48:59 -0800 (PST) Message-ID: <1028289087.1234248539704.JavaMail.jira@brutus> Date: Mon, 9 Feb 2009 22:48:59 -0800 (PST) From: "Amar Kamat (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-5083) Optionally a separate daemon should serve JobHistory In-Reply-To: <644178812.1232443799608.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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 {code} -1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 17 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 3 new Findbugs warnings. [exec] [exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity. [exec] [exec] -1 release audit. The applied patch generated 835 release audit warnings (more than the trunk's current 832 warnings). {code} 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, 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.