Re: Hadoop's deafult FIFO scheduler

2010-10-23 Thread He Chen
I checked the job history, The setup process finished in order. On Fri, Oct 22, 2010 at 10:12 PM, Hemanth Yamijala wrote: > 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

Re: Hadoop's deafult FIFO scheduler

2010-10-22 Thread Hemanth Yamijala
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

Re: Hadoop's deafult FIFO scheduler

2010-10-15 Thread He Chen
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 wrote: > Hi, > > On Thu, Oct 14, 2010 at 10:59 PM, He Chen wrote: > > they arrived in 1 minute. I understand there will be

Re: Hadoop's deafult FIFO scheduler

2010-10-14 Thread Hemanth Yamijala
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 which > 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 w

Re: Hadoop's deafult FIFO scheduler

2010-10-14 Thread He Chen
I doubt this. According to the execution record. the disk and network utilization are the same. At last, if the FCFS scheduler only apply for the setup stage which takes about several second. This does not mean anything. users who submit their jobs earlier only ge job setup earlier, but may be del

Re: Hadoop's deafult FIFO scheduler

2010-10-14 Thread Nan Zhu
Hi, Chen I think it's due to the disk/network performance, I mean the speed of reading the content on disk/network into the local memory if job3 hasn't complete data to start mappers, but job4 does, the scheduler would select the tasks of job4 from the list to run firstly, I think the so called

Re: Hadoop's deafult FIFO scheduler

2010-10-14 Thread He Chen
they arrived in 1 minute. I understand there will be a setup phase which will use any free slot no matter map or reduce. My queue time is the period between the start of Map stage and the time job is submitted. Because the setup phase has the higher priority than map and reduce tasks. Any job subm

Re: Hadoop's deafult FIFO scheduler

2010-10-14 Thread abhishek sharma
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 1