Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 58703 invoked from network); 30 Jan 2009 13:06:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jan 2009 13:06:29 -0000 Received: (qmail 21625 invoked by uid 500); 30 Jan 2009 13:06:23 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 21592 invoked by uid 500); 30 Jan 2009 13:06:23 -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 21580 invoked by uid 99); 30 Jan 2009 13:06:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2009 05:06:23 -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; Fri, 30 Jan 2009 13:06:21 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A8177234C4AF for ; Fri, 30 Jan 2009 05:05:59 -0800 (PST) Message-ID: <329955139.1233320759687.JavaMail.jira@brutus> Date: Fri, 30 Jan 2009 05:05:59 -0800 (PST) From: "Amar Kamat (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4934) Distinguish running/successful/failed/killed jobs in jobtracker's history In-Reply-To: <1267404736.1230014744182.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-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668855#action_12668855 ] Amar Kamat commented on HADOOP-4934: ------------------------------------ I propose : # Allow users to group/browse jobs based on various parameters like time(month/week/day/hour), user, jobname. One way to do it is to store job history files under the user folder, grouped by date instead of storing it in a flat structure. So a user a will have the jobhistory files as _job-history-folder/user-name/day/job-history-file_. This will help when there are too many files in the jobhistory folder. # Running/Pending/Killed/Failed jobs should not be shown as there is no point to show it in history. One optimization in the above approach would be to have a 3rd level of hierarchy in terms of job state. So a running job history file will be stored as _job-history-folder/user-name/day/running/job-history-file_ # By default show last 100 jobs and allow users to change this value via the web-ui > Distinguish running/successful/failed/killed jobs in jobtracker's history > ------------------------------------------------------------------------- > > Key: HADOOP-4934 > URL: https://issues.apache.org/jira/browse/HADOOP-4934 > Project: Hadoop Core > Issue Type: Improvement > Components: mapred > Affects Versions: 0.21.0 > Reporter: Amar Kamat > Fix For: 0.21.0 > > > It would be nice to group jobs in jobtracker's history based on their completion status. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.