Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 24457 invoked from network); 23 Jun 2009 02:56:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Jun 2009 02:56:18 -0000 Received: (qmail 92391 invoked by uid 500); 23 Jun 2009 02:56:27 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 92293 invoked by uid 500); 23 Jun 2009 02:56:27 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 92283 invoked by uid 99); 23 Jun 2009 02:56:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jun 2009 02:56:27 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jason.hadoop@gmail.com designates 209.85.146.177 as permitted sender) Received: from [209.85.146.177] (HELO wa-out-1112.google.com) (209.85.146.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jun 2009 02:56:18 +0000 Received: by wa-out-1112.google.com with SMTP id j32so510854waf.29 for ; Mon, 22 Jun 2009 19:55:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=F+HcnTPonESsoUzoF50OYufiXgP04YvWySUf8dLyoSA=; b=pQgukeeRX0t65gusotbacQl7pjLrkCi8tk3gwl6RAhoRYcdJ5RaLmwrgaWlmSp8SFj l18xTycSKGhLSkOePY0PbrUp3d0ecmRrWJ2Sgu0Qrsyjr3FPgsiU0/acLJAzw+0/Ah88 2xByijfa8rTp6nCRAEQl1nC4fqXmcFLZf8PnI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hQYjGPrHOaMYvTcA7vNnKnhdehoKOPQIm7q5iFX1SobL8Fuz2H0fp/+qscOYs38rub CYJkVMRHsXQMXAPVGP6UzlbMgFjsDhS9EIvkv/6HdFNl+3VGNjbBaE1AFzztSnRFwq9U ijeEsNTEOhYPndjCUOpFu/jcWpzDdKOKqNux4= MIME-Version: 1.0 Received: by 10.115.91.2 with SMTP id t2mr6000300wal.224.1245725757703; Mon, 22 Jun 2009 19:55:57 -0700 (PDT) In-Reply-To: <1e7471d50906220923o7379f748k2e7bb4d4a5d9cbe3@mail.gmail.com> References: <1e7471d50906220923o7379f748k2e7bb4d4a5d9cbe3@mail.gmail.com> Date: Mon, 22 Jun 2009 19:55:57 -0700 Message-ID: <314098690906221955s3a5045f2t5ecc39b0ca4ac178@mail.gmail.com> Subject: Re: When is configure and close run From: jason hadoop To: core-user@hadoop.apache.org, saptarshi.guha@gmail.com Content-Type: multipart/alternative; boundary=00163646d8f246efde046cfb211b X-Virus-Checked: Checked by ClamAV on apache.org --00163646d8f246efde046cfb211b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit configure and close are run for each task, mapper and reducer. The configure and close are NOT run on the combiner class. On Mon, Jun 22, 2009 at 9:23 AM, Saptarshi Guha wrote: > Hello, > In a mapreduce job, a given map JVM will run N map tasks. Are the > configure and close methods executed for every one of these N tasks? > Or is configure executed once when the JVM starts and the close method > executed once when all N have been completed? > > I have the same question for the reduce task. Will it be run before > for every reduce task? And close is run when all the values for a > given key have been processed? > > We can assume there isn't a combiner. > > Regards > Saptarshi > -- Pro Hadoop, a book to guide you from beginner to hadoop mastery, http://www.amazon.com/dp/1430219424?tag=jewlerymall www.prohadoopbook.com a community for Hadoop Professionals --00163646d8f246efde046cfb211b--