Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 48385 invoked from network); 23 Oct 2010 03:13:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Oct 2010 03:13:12 -0000 Received: (qmail 13724 invoked by uid 500); 23 Oct 2010 03:13:11 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 13609 invoked by uid 500); 23 Oct 2010 03:13:11 -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 13600 invoked by uid 99); 23 Oct 2010 03:13:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Oct 2010 03:13:11 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yhemanth@gmail.com designates 209.85.160.176 as permitted sender) Received: from [209.85.160.176] (HELO mail-gy0-f176.google.com) (209.85.160.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Oct 2010 03:13:06 +0000 Received: by gyg4 with SMTP id 4so1296112gyg.35 for ; Fri, 22 Oct 2010 20:12:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=RJ8uRkHEUaFgbxGStuNvoWFdDrg1uUwkQpQ57ELeOWk=; b=WAJLiptS9CGctytGT/RjHqpdDKbUfAmezErCrkj/lskZ4hlNbh1Ihgn/2sVvacJkRl xNrtqG1eC0uo96pCNyTQxXwu7I+8Xek27NPQ2g8TjIJScaIr+u/jdCf1Mtsd/1Op7QNP 5hCHG0TGGEIZqM0MVNO/nNesWWsjVI3qbK+cI= 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:content-transfer-encoding; b=PxsdcR8nVTwlvK2FSrH9Ni0eeCi7El2SEMq92buBU11aMKJeKHIV5DqSaTpQH3TPyr E/jds7ll4nnRQsdnvBh+Gxw1J8MlhlaXMIf6VzMLnONkDX91k3Ps31sEv+oXT51TNnu6 hiOri5JI3ySiklIJWbeGL8OavHqw5mmY/TUXA= MIME-Version: 1.0 Received: by 10.151.44.20 with SMTP id w20mr3850998ybj.276.1287803564994; Fri, 22 Oct 2010 20:12:44 -0700 (PDT) Received: by 10.220.187.8 with HTTP; Fri, 22 Oct 2010 20:12:44 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Oct 2010 08:42:44 +0530 Message-ID: Subject: Re: Hadoop's deafult FIFO scheduler From: Hemanth Yamijala To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Sorry for a delayed response. Once jobs are submitted, they are setup by running the setup task. These are run in order of submission. However, the setup task itself runs on any free map or reduce slot on any node. I can imagine scenarios where the setup task of a job that was submitted later completes first. And when that happens, it can start running out of order. Thanks Hemanth On Fri, Oct 15, 2010 at 3:41 PM, He Chen wrote: > Hi Hemanth > > all jobs were submitted within a minute and a few > seconds between jobs. The hadoop version is 0.20.2 > > Thanks > > > On Thu, Oct 14, 2010 at 11:45 PM, Hemanth Yamijala wr= ote: > >> Hi, >> >> On Thu, Oct 14, 2010 at 10:59 PM, He Chen wrote: >> > they arrived in 1 minute. I understand there will be a setup phase whi= ch >> > will use any free slot no matter map or reduce. >> > >> >> You mean all jobs were submitted within a minute ? That means a few >> seconds between jobs ? Or do you mean each job was submitted a minute >> after the earlier job. Also, which version of Hadoop is this ? >> >> > My queue time is the period between the start of Map stage and the tim= e >> job >> > is submitted. Because the setup phase has the higher priority than map >> and >> > reduce tasks. Any job submitted in the queue will setup no matter how >> many >> > previous map and reduce tasks need to be assigned. >> > >> > Now, I am sure the job3 setup stage finished earlier than job4's. >> However, >> > job3's map stage start later than job4's. BTW, they request same amoun= t >> of >> > blocks. >> > >> > >> > On Thu, Oct 14, 2010 at 12:10 PM, abhishek sharma >> wrote: >> > >> >> What is the inter-arrival time between these jobs? >> >> >> >> There is a "set up" phase for jobs before they are launched. It is >> >> possible that the order of jobs can change due to slightly different >> >> set up times. Apart from the number of blocks, it may matter "where" >> >> these blocks lie. >> >> >> >> Abhishek >> >> >> >> On Thu, Oct 14, 2010 at 10:06 AM, He Chen wrote: >> >> > Hi all >> >> > >> >> > I am testing the performance of my Hadoop clsuters with Hadoop Defa= ult >> >> FIFO >> >> > schedular. But I find a interesting phenomina. >> >> > >> >> > When I submit a series of jobs, some job will be executed earlier e= ven >> >> they >> >> > are submitted late. All jobs are request same amount of blocks. For >> >> example: >> >> > job 1 =A0submit at time 0 >> >> > job 2 submit at time 1 >> >> > job 3 submit at time 2 >> >> > job 4 submit at time 3 >> >> > >> >> > >> >> > job 4 's queue time is smaller than job3's queue time. This disobey >> the >> >> FIFO >> >> > principle. Any one can give a hint? >> >> > >> >> > Thanks >> >> > >> >> > Chen >> >> > >> >> >> > >> >