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 6454C1764E for ; Sat, 21 Mar 2015 23:17:15 +0000 (UTC) Received: (qmail 40812 invoked by uid 500); 21 Mar 2015 23:17:10 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 40746 invoked by uid 500); 21 Mar 2015 23:17:10 -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 40735 invoked by uid 99); 21 Mar 2015 23:17:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Mar 2015 23:17:10 +0000 Date: Sat, 21 Mar 2015 23:17:10 +0000 (UTC) From: "Gera Shegalov (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly. 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-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14373093#comment-14373093 ] Gera Shegalov commented on MAPREDUCE-6286: ------------------------------------------ +1, Thanks for spotting the bug, [~zxu]! [~qwertymaniac], do you mind committing to branch-2.7 as well? It looks like a safe change. > A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly. > ----------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-6286 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: client > Affects Versions: 2.6.0 > Reporter: zhihai xu > Assignee: zhihai xu > Fix For: 2.8.0 > > Attachments: MAPREDUCE-6286.000.patch > > > A typo in HistoryViewer makes some code useless and it causes counter limits are not reset correctly. > The typo is > Limits.reset(conf); > We should use jobConf instead of conf. > With the typo, the following code becomes useless: > {code} > final Path jobConfPath = new Path(jobFile.getParent(), jobDetails[0] > + "_" + jobDetails[1] + "_" + jobDetails[2] + "_conf.xml"); > final Configuration jobConf = new Configuration(conf); > jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString()); > {code} > The code wants to load the configuration from the Job configuration file and reset the Limits based on the new configuration loaded from the Job configuration file. But with the typo, the Limits are reset with the old configuration. > So this typo is apparent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)