This error occurs when several reducers are unable to fetch the given map output ( attempt_200907202331_0001_m_000001_0 in your example). I am guessing that there is a configuration issue in your setup -- the reducers are not able to contact/transfer map outputs from the TaskTracker. The TT log on the node where the map ran could throw some light on the error. Could you verify if all the nodes in your cluster are able to connect with others? You could also manually login to the reducer node and try pulling the map output yourself and see what error you are getting.
Cheers Jothi On 7/21/09 12:33 PM, "George Pang" <p09...@gmail.com> wrote: > Hi users, > > I got this "Too many fetch failures" in the following error message: > > *09/07/20 23:33:39 INFO mapred.JobClient: map 100% reduce 16% > 09/07/20 23:46:22 INFO mapred.JobClient: Task Id : > attempt_200907202331_0001_m_000001_0, Status : FAILED > Too many fetch-failures > 09/07/20 23:46:37 INFO mapred.JobClient: Job complete: job_200907202331_0001 > > *Don't know why it always stops at reduce 16% then assumes. It take a long > time even to run a small task. > > I saw people asking the same question in previous mail list, but I don't get > the help I need. > > Hadoop version: 0.18.3 > Ubuntu version: 8.04 > > Thank you in advance! > > George
