Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 24398 invoked from network); 22 Feb 2010 21:02:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Feb 2010 21:02:51 -0000 Received: (qmail 47769 invoked by uid 500); 22 Feb 2010 21:02:51 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 47685 invoked by uid 500); 22 Feb 2010 21:02:51 -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 47446 invoked by uid 99); 22 Feb 2010 21:02:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2010 21:02:50 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2010 21:02:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id ED0D529A0024 for ; Mon, 22 Feb 2010 13:02:27 -0800 (PST) Message-ID: <2144217080.441201266872547970.JavaMail.jira@brutus.apache.org> Date: Mon, 22 Feb 2010 21:02:27 +0000 (UTC) From: "Todd Lipcon (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-1521) Protection against incorrectly configured reduces In-Reply-To: <1908021124.435731266860670261.JavaMail.jira@brutus.apache.org> 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-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836902#action_12836902 ] Todd Lipcon commented on MAPREDUCE-1521: ---------------------------------------- This makes me just a little bit nervous - the case I'm worried about is when a job is working fine in production and then starts failing at 3am some morning because the data volume increased just a little bit over the threshold. Could we default this behavior off and only turn it on for clusters where the operators prefer it? > Protection against incorrectly configured reduces > ------------------------------------------------- > > Key: MAPREDUCE-1521 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1521 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: jobtracker > Reporter: Arun C Murthy > Assignee: Arun C Murthy > Priority: Critical > Fix For: 0.22.0 > > > We've seen a fair number of instances where naive users process huge data-sets (>10TB) with badly mis-configured #reduces e.g. 1 reduce. > This is a significant problem on large clusters since it takes each attempt of the reduce a long time to shuffle and then run into problems such as local disk-space etc. Then it takes 4 such attempts. > Proposal: Come up with heuristics/configs to fail such jobs early. > Thoughts? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.