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 6F8B895F7 for ; Wed, 15 Feb 2012 18:09:26 +0000 (UTC) Received: (qmail 91921 invoked by uid 500); 15 Feb 2012 18:09:26 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 91893 invoked by uid 500); 15 Feb 2012 18:09:26 -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 91885 invoked by uid 99); 15 Feb 2012 18:09:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 18:09:26 +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; Wed, 15 Feb 2012 18:09:20 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id B2BE71B9F5F for ; Wed, 15 Feb 2012 18:08:59 +0000 (UTC) Date: Wed, 15 Feb 2012 18:08:59 +0000 (UTC) From: "Harsh J (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1438134343.41515.1329329339733.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <395403508.30234.1313094987497.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-2835) Make per-job counter limits configurable 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-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208624#comment-13208624 ] Harsh J commented on MAPREDUCE-2835: ------------------------------------ I agree with Brian's reasoning. I understand that if you place a configuration and a newbie user/ops encounters it, they'll just raise it without second consideration. We need to address such best practices with docs/warn logs (logs can warn with hard numbers), rather than magic numbers that would not fit every one/every case. > Make per-job counter limits configurable > ---------------------------------------- > > Key: MAPREDUCE-2835 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2835 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Affects Versions: 0.20.204.0 > Reporter: Tom White > Assignee: Tom White > Attachments: MAPREDUCE-2835.patch, MAPREDUCE-2835.patch > > > The per-job counter limits introduced in MAPREDUCE-1943 are fixed, except for the total number allowed per job (mapreduce.job.counters.limit). It would be useful to make them all configurable. -- 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