The job may have succeeded due to the task having run successfully on another tasktracker after a retry attempt was scheduled. This probably means one of your TT has something bad on it, and should be easily identifiable from the UI.
If all TTs are bad, your job would fail -- so yes, better to fix than worry about expecting failures. On Mon, Jul 11, 2011 at 11:53 PM, C.V.Krishnakumar Iyer <f2004...@gmail.com> wrote: > Hi, > > I get this error too. But the Job completes properly. Is this error any cause > for concern? As in, would any computation be hampered because of this? > > Thanks ! > > Regards, > Krishnakumar > On Jul 11, 2011, at 10:53 AM, Bharath Mundlapudi wrote: > >> That number is around 40K (I think). I am not sure if you have certain >> configurations to cleanup user task logs periodically. We have solved this >> problem in MAPREDUCE-2415 which part of 0.20.204. >> >> >> But you cleanup the task logs periodically, you will not run into this >> problem. >> >> -Bharath > > -- Harsh J
