Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 70030 invoked from network); 22 Apr 2010 12:51:43 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Apr 2010 12:51:43 -0000 Received: (qmail 8913 invoked by uid 500); 22 Apr 2010 12:51:42 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 8736 invoked by uid 500); 22 Apr 2010 12:51:41 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 8728 invoked by uid 99); 22 Apr 2010 12:51:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 12:51:41 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=AWL,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of msegel@navteq.com designates 204.120.70.37 as permitted sender) Received: from [204.120.70.37] (HELO xmailfargo.navteq.com) (204.120.70.37) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 12:51:34 +0000 Received: from fargo-spamfw.navteq.com (navteq-spamfw.navteq.com [10.6.10.131]) by xmailfargo.navteq.com (8.13.6/8.13.6) with ESMTP id o3MCY1mD025816 for ; Thu, 22 Apr 2010 07:34:01 -0500 Received: from imailfargo.navteq.com (localhost [127.0.0.1]) by fargo-spamfw.navteq.com (Spam & Virus Firewall) with ESMTP id 38CEA47F4837 for ; Thu, 22 Apr 2010 07:51:13 -0500 (CDT) Received: from imailfargo.navteq.com (imailfargo.navteq.com [10.6.10.130]) by fargo-spamfw.navteq.com with ESMTP id IY90EDLo64H53ECG for ; Thu, 22 Apr 2010 07:51:13 -0500 (CDT) Received: from hq-ex-ht02.ad.navteq.com ([10.8.222.172]) by imailfargo.navteq.com (8.13.6/8.13.6) with ESMTP id o3MCpCZF023730 for ; Thu, 22 Apr 2010 07:51:13 -0500 Received: from hq-ex-mb02.ad.navteq.com ([fe80::880d:318e:e860:a8db]) by hq-ex-ht02.ad.navteq.com ([fe80::24f6:ca50:734d:df6e%14]) with mapi; Thu, 22 Apr 2010 07:51:13 -0500 From: "Segel, Mike" To: "common-dev@hadoop.apache.org" Date: Thu, 22 Apr 2010 07:51:11 -0500 Subject: RE: [jira] Created: (HADOOP-6720) 'Killed' jobs and 'Failed' jobs should be displayed seperately in JT UI Thread-Topic: [jira] Created: (HADOOP-6720) 'Killed' jobs and 'Failed' jobs should be displayed seperately in JT UI Thread-Index: Acrh/mwwLFpd1amxTC6Q5Put/DXOQQAG9OVQ Message-ID: References: <15847331.135771271928590537.JavaMail.jira@thor> In-Reply-To: <15847331.135771271928590537.JavaMail.jira@thor> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-NAIMIME-Disclaimer: 1 X-NAIMIME-Modified: 1 I would disagree. Its important to avoid 'information overload'. Since you can drill down by following the link, you can see the task's state. Whether it was killed or it failed. So it is currently possible to see this in the JT UI. -Mike -----Original Message----- From: Subramaniam Krishnan (JIRA) [mailto:jira@apache.org] Sent: Thursday, April 22, 2010 4:30 AM To: common-dev@hadoop.apache.org Subject: [jira] Created: (HADOOP-6720) 'Killed' jobs and 'Failed' jobs should be displayed seperately in JT UI 'Killed' jobs and 'Failed' jobs should be displayed seperately in JT UI ------------------------------------------------------------------------ Key: HADOOP-6720 URL: https://issues.apache.org/jira/browse/HADOOP-6720 Project: Hadoop Common Issue Type: New Feature Environment: all Reporter: Subramaniam Krishnan Assignee: Subramaniam Krishnan Priority: Critical Fix For: 0.19.0 It is not possible, via APIs, to know if a job has been killed, only that has not been successful. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.