Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 72626 invoked from network); 22 Sep 2008 04:16:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Sep 2008 04:16:06 -0000 Received: (qmail 74495 invoked by uid 500); 22 Sep 2008 04:15:58 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 74465 invoked by uid 500); 22 Sep 2008 04:15:58 -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 74454 invoked by uid 99); 22 Sep 2008 04:15:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Sep 2008 21:15:58 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pku.gaoqin@gmail.com designates 209.85.128.184 as permitted sender) Received: from [209.85.128.184] (HELO fk-out-0910.google.com) (209.85.128.184) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Sep 2008 04:14:59 +0000 Received: by fk-out-0910.google.com with SMTP id 26so1456410fkx.13 for ; Sun, 21 Sep 2008 21:15:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=GRADmc563qRIR+AAdWMeHH0bvcGZ2k72h4DtlUXIuwI=; b=p5jbO42BejGn8XuYw9TiMTmGXtuRT3aLU+qnXfzpANupIrBQA7E/RZ9N+4TjVowOzH /h5gYB4aZPMZsZ0yv7tiL1F4Xt7pV8RCUUoadJ4rc/Um9V5STTLKsxzI63cLXjd7Zu8U xJ7ydLJTABTk3v+BGx+zqCIWE65phLr8WooCw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=o+3JtSO4Vk9AUsVCmA7GtSBj7Q17yKj9q1b5hQ/OUrMlVRbUb5qu6bRgHM6Mw5e48g H/P/z1LRhcjjKjUNzGeTiRNy2KO5RZoW2mSQ8HPyILPwRGhbNSFc0d0rs93+jGitY1n2 bW+EqjPftwCrrKUIkqvQf8EkGUHYNwNDvrwss= Received: by 10.187.245.13 with SMTP id x13mr367315far.26.1222056931365; Sun, 21 Sep 2008 21:15:31 -0700 (PDT) Received: by 10.187.161.15 with HTTP; Sun, 21 Sep 2008 21:15:31 -0700 (PDT) Message-ID: <826304a60809212115p6c7cfdc6h8ee9395a0b986f90@mail.gmail.com> Date: Mon, 22 Sep 2008 00:15:31 -0400 From: "Qin Gao" Sender: pku.gaoqin@gmail.com To: core-user@hadoop.apache.org Subject: Re: is combiner output written to disk? In-Reply-To: <257c70550809212108s723af39dqf37a7800adf9051b@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2513_10874267.1222056931379" References: <257c70550809212108s723af39dqf37a7800adf9051b@mail.gmail.com> X-Google-Sender-Auth: f2dfad5c67af7168 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2513_10874267.1222056931379 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline I think it will be written to disk. There will be no difference in output format or flow with or without combiner. On Mon, Sep 22, 2008 at 12:08 AM, Sandy wrote: > Just a quick clarification: > > The combiner function acts as an optimization between the map and the > reduce > phases. Is the output of the combiner phase stored in memory before being > handed to reduce? Or is it written to disk and subsequently read from disk > by the reduce phase? > > > Thanks in advance, > > -SM > ------=_Part_2513_10874267.1222056931379--