No, this is expected. A correction - it's not all tasks, just map-tasks of currently active jobs which are re-executed.
Ravi Teja explained why in his previous response to this same question. Arun On Sep 29, 2011, at 9:14 AM, Leonardo Gamas wrote: > Hi, > > I have a very large MapReduce Job and sometimes a TaskTracker doesn't send a > heartbeat in the preconfigured amount of time, so it's considered dead. It's > ok, but all tasks already finished by this TaskTracker are lost too, or > better explained, are rescheduled and re-executed by another TaskTracker. > > This is a default behavior or i'm experiencing some bug or miss > configuration? > > My reguards, > > Leonardo Gamas
