I was just wondering what goes on under the covers once the last reduce task ends. The following is from a very simple map reduce I run throughout the day. Typically the run time is about a minute from start to end, but for this particular run there was a delay of over 5 minutes after the last reduce task ended.
Any thoughts? Thanks, -James Warren 2010-05-07 01:11:10,302 [main] INFO org.apache.hadoop.mapred.JobClient - Running job: job_201005041742_0879 2010-05-07 01:11:11,305 [main] INFO org.apache.hadoop.mapred.JobClient - map 0% reduce 0% 2010-05-07 01:11:49,410 [main] INFO org.apache.hadoop.mapred.JobClient - map 4% reduce 0% 2010-05-07 01:11:55,427 [main] INFO org.apache.hadoop.mapred.JobClient - map 8% reduce 0% 2010-05-07 01:12:04,454 [main] INFO org.apache.hadoop.mapred.JobClient - map 17% reduce 0% 2010-05-07 01:12:07,462 [main] INFO org.apache.hadoop.mapred.JobClient - map 17% reduce 2% 2010-05-07 01:12:10,471 [main] INFO org.apache.hadoop.mapred.JobClient - map 26% reduce 2% 2010-05-07 01:12:16,487 [main] INFO org.apache.hadoop.mapred.JobClient - map 43% reduce 5% 2010-05-07 01:12:19,497 [main] INFO org.apache.hadoop.mapred.JobClient - map 100% reduce 5% 2010-05-07 01:12:22,505 [main] INFO org.apache.hadoop.mapred.JobClient - map 100% reduce 14% 2010-05-07 01:12:31,530 [main] INFO org.apache.hadoop.mapred.JobClient - map 100% reduce 100% 2010-05-07 01:18:06,367 [main] INFO org.apache.hadoop.mapred.JobClient - Job complete: job_201005041742_0879
