In the past, when I've observed this kind of insane behavior (no job should take 40 minutes to submit), it's been due the NameNode or the JobTracker being extremely overloaded, responding slowly, causing timeouts+retries.
2011/12/28 Thejas Nair <[email protected]> > I haven't seen/heard this issue. > Do you mean to say that the extra time is actually a delay before MR job > is launched ? > Did you have free map/reduce slots when you ran pig job from trunk ? > > Thanks, > Thejas > > > > > On 12/23/11 9:01 PM, Yang Ling wrote: > >> I have a Pig job typically finish in 20 minutes. I tried Pig code from >> trunk, it takes more than 1 hours to finish. My input and output are on >> Amazon s3. One interesting thing is it takes about 40 minutes to start the >> mapreduce job, but for 0.9.1 release, it takes only less than 1 minute. Any >> idea? >> > >
