Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 65676 invoked from network); 3 Aug 2009 03:57:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Aug 2009 03:57:57 -0000 Received: (qmail 65593 invoked by uid 500); 3 Aug 2009 03:58:01 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 65520 invoked by uid 500); 3 Aug 2009 03:58:01 -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 65499 invoked by uid 99); 3 Aug 2009 03:57:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 03:57:57 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [69.147.107.20] (HELO mrout1-b.corp.re1.yahoo.com) (69.147.107.20) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 03:57:46 +0000 Received: from [192.168.1.64] (snvvpn2-10-72-76-c214.hq.corp.yahoo.com [10.72.76.214]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id n733v3es041870; Sun, 2 Aug 2009 20:57:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=cc:message-id:from:to:in-reply-to:content-type: content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=RmYWh/a2Ni9++wvKR5mS0i9AAxGBuhDjlfeWLsebxK+8Y3HKJ6n3AU5ZVi4x3sRS Cc: common-dev@hadoop.apache.org Message-Id: <63609015-F12D-4054-BF96-3D8477036747@yahoo-inc.com> From: Arun C Murthy To: mapreduce-dev@hadoop.apache.org In-Reply-To: <1c9a863e0908020502n7d810962rbc561437388fce84@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: why reduce task can be scheduled before map tasks are 100% completed? Date: Sun, 2 Aug 2009 20:57:05 -0700 References: <1c9a863e0908020502n7d810962rbc561437388fce84@mail.gmail.com> X-Mailer: Apple Mail (2.935.3) X-Virus-Checked: Checked by ClamAV on apache.org That check ensures sufficient #maps are completed before any of the =20 reduces for the job are started. The reduces 'shuffle' map outputs from completed maps, but don't get =20 into the 'reduce' phase until all map-outputs are copied over. Arun PS: Moving this to mapreduce-dev@ On Aug 2, 2009, at 5:02 AM, =E6=88=91=E7=9A=84Gmail=E9=82=AE=E7=AE=B1 = wrote: > Hi, everyone. > In class org.apache.hadoop.mapred.JobInProgress, there is a public =20 > method: > scheduleReduces(), it will return true if "finishedMapTasks >=3D > completedMapsForReduceSlowstart" > and then the scheduler can schedule a new reduce task for a given > taskTracker. > > but as I konw, reduce can not be started unitl map is 100% =20 > completed. Does > anyone can explain it? thanks a lot.