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 D5CFB9650 for ; Tue, 21 Feb 2012 19:30:13 +0000 (UTC) Received: (qmail 75209 invoked by uid 500); 21 Feb 2012 19:30:13 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 75173 invoked by uid 500); 21 Feb 2012 19:30:13 -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 75163 invoked by uid 99); 21 Feb 2012 19:30:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 19:30:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 19:30:07 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 80A581C268D for ; Tue, 21 Feb 2012 19:29:46 +0000 (UTC) Date: Tue, 21 Feb 2012 19:29:46 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1566113963.313.1329852586528.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <286285337.21956.1312930047288.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-2793) [MR-279] Maintain consistency in naming appIDs, jobIDs and attemptIDs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212827#comment-13212827 ] Hadoop QA commented on MAPREDUCE-2793: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12515465/MAPREDUCE-2793-branch-0.23.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 21 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesTasks org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesAttempts +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1904//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1904//console This message is automatically generated. > [MR-279] Maintain consistency in naming appIDs, jobIDs and attemptIDs > ---------------------------------------------------------------------- > > Key: MAPREDUCE-2793 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2793 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Ramya Sunil > Assignee: Bikas Saha > Priority: Critical > Fix For: 0.23.2 > > Attachments: MAPREDUCE-2793-branch-0.23.patch, MAPREDUCE-2793-branch-0.23.patch, MAPREDUCE-2793-branch-0.23.patch, MAPREDUCE-2793-branch-0.23.patch, MAPREDUCE-2793.patch > > > appIDs, jobIDs and attempt/container ids are not consistently named in the logs, console and UI. For consistency purpose, they all have to follow a common naming convention. > Currently, > For appID > ========= > On the RM UI: app_1308259676864_5 > On the JHS UI: No appID > Console/logs: No appID > mapred-local dirs are named as: application_1308259676864_0005 > For jobID > ========= > On the RM UI: job_1308259676864_5_5 > JHS UI: job_1308259676864_5_5 > Console/logs: job_1308259676864_0005 > mapred-local dirs are named as: No jobID > For attemptID > ============ > On the RM UI: attempt_1308259676864_5_5_m_24_0 > JHS attempt_1308259676864_5_5_m_24_0 > Console/logs: attempt_1308259676864_0005_m_000024_0 > mapred-local dirs are named as: container_1308259676864_0005_000024 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira