Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC012DE9E for ; Mon, 8 Oct 2012 17:52:03 +0000 (UTC) Received: (qmail 20222 invoked by uid 500); 8 Oct 2012 17:52:03 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 20175 invoked by uid 500); 8 Oct 2012 17:52:03 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 20166 invoked by uid 99); 8 Oct 2012 17:52:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2012 17:52:03 +0000 Date: Mon, 8 Oct 2012 17:52:03 +0000 (UTC) From: "Robert Joseph Evans (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1141218763.9414.1349718723409.JavaMail.jiratomcat@arcas> In-Reply-To: <1355244933.2562.1349469002914.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (MAPREDUCE-4711) Append time elapsed since job-start-time for finished tasks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471696#comment-13471696 ] Robert Joseph Evans commented on MAPREDUCE-4711: ------------------------------------------------ The patch looks OK to me, but I don't know if I like seeing all of the extra text in the table. It starts to make the table very crowded and busy and it already is too overcrowded for my taste. I would much rather have something visual then have a huge table with all of this information in it, but that is probably a ways off. Perhaps we could look at adding in something to show/hide columns so we don't need to see everything, and if someone wants to dig deeper into an issue they can add in more columns. Alternatively I would not mind having an analyze this job link like in 1.0, at least until something better can be determined. I also noticed that there appears to be a bug in the history server. It is reporting the task start time to be the same as the job start time (or at least the time that the task was initialized by the AM). In both 1.x and in the AM the task start time is the start time of the first task attempt. We need to file a JIRA for this too or else your new time is always going to be the same as the column right next to it. > Append time elapsed since job-start-time for finished tasks > ----------------------------------------------------------- > > Key: MAPREDUCE-4711 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4711 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver > Affects Versions: 0.23.3 > Reporter: Ravi Prakash > Assignee: Ravi Prakash > Attachments: MAPREDUCE-4711.branch-0.23.patch > > > In 0.20.x/1.x, the analyze job link gave this information > bq. The last Map task task_ finished at (relative to the Job launch time): 5/10 20:23:10 (1hrs, 27mins, 54sec) > The time it took for the last task to finish needs to be calculated mentally in 0.23. I believe we should print it next to the finish time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira