Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 29164D846 for ; Tue, 28 Aug 2012 15:29:33 +0000 (UTC) Received: (qmail 47092 invoked by uid 500); 28 Aug 2012 15:29:31 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 47025 invoked by uid 500); 28 Aug 2012 15:29:31 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 47016 invoked by uid 99); 28 Aug 2012 15:29:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2012 15:29:31 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2012 15:29:25 +0000 Received: by obbtb18 with SMTP id tb18so9845057obb.35 for ; Tue, 28 Aug 2012 08:29:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=x5xvcFo2o/NJCTQdzihZy9yw7DlDh+PcEekbx1epePM=; b=hYiVyXhB/ob7bx9vHqRVsnDnQhEAJoPo5FE8Q2aJPdyJspt2dMuBLxNafUc3MJxomg BLFVdttIKHPHIL+sp1jQxq8Esgr5uP36lz8nwj2KAxfj2fxWZpOebt2nAk+zNhht0mB1 ZoKfmTmlHcylFaTdIgaUjo59S/dvhfdxeHxF0ZeTXHFsqhAQUA33wAkNOH7fwd0UqADT +uBWaCScP5I8OwkFzBrMYUeCAcUdTMUva7S4qp4DW5wveYpt/nufxjKzmtQSRI6Y6vYd tC96kHzfONgu12yyq0nakzRZ4aExybwx/rh0CkU9w2Xd4JTp5FzbL8oCEEGmJw0jA48n jyhg== Received: by 10.60.22.167 with SMTP id e7mr12789385oef.35.1346167744249; Tue, 28 Aug 2012 08:29:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.11.168 with HTTP; Tue, 28 Aug 2012 08:28:44 -0700 (PDT) In-Reply-To: References: <1BE739D4-365E-41D8-9840-88B779F1E427@gmail.com> From: Harsh J Date: Tue, 28 Aug 2012 20:58:44 +0530 Message-ID: Subject: Re: Number of reducers To: abhiTowson cal Cc: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlLguBp8KKslgBuJay6crKHSE7b+T2EQTGTvvYrEORI3e4+ciq1CDbhdk4uNcI3K/rYNxxe Ah, well, my bad. See instead the description for mapred.reduce.tasks in mapred-default.xml, which states this: "Typically set to 99% of the cluster's reduce capacity, so that if a node fails the reduces can still be executed in a single wave." FWIW, I set it manually to the level of parallelism I require (given my partitioned data, etc.). On Tue, Aug 28, 2012 at 8:43 PM, abhiTowson cal wrote: > hi harsh, > > Thanks for the reply.I get your first and second points and coming to > third point how is it specific to a job? > My question was specific to job. > > Regards > Abhishek > > > > On Mon, Aug 27, 2012 at 11:29 PM, Harsh J wrote: >> Hi, >> >> On Tue, Aug 28, 2012 at 8:32 AM, Abhishek wrote: >>> Hi all, >>> >>> I just want to know that, based on what factor map reduce framework decides number of reducers to launch for a job >> >> The framework does not auto-determine the number of reducers for a >> job. That is purely user-or-client-program-supplied presently. >> >>> By default only one reducer will be launched for a given job is this right? If we explicitly does not mention number to launch via command line or driver class. >> >> Yes, by default the number of reduce tasks is configured to be one. >> >>> If i choose to decide number of reducers to mention explicitly, what should I consider.Because choosing in appropriate number of reducer hampers the performance. >> >> See http://wiki.apache.org/hadoop/HowManyMapsAndReduces >> >> -- >> Harsh J -- Harsh J