It is a "not enough information" error. Check the tasks, jobtracker, tasktracker, datanode, and namenode logs.
On Sep 21, 2010, at 12:30 PM, C.V.Krishnakumar wrote: > > Hi, > Just wanted to know if anyone has any idea about this one? This happens every > time I run a job. > Is this issue hardware related? > > Thanks in advance, > Krishnakumar. > > Begin forwarded message: > >> From: "C.V.Krishnakumar" <[email protected]> >> Date: September 17, 2010 1:32:49 PM PDT >> To: [email protected] >> Subject: Tasks Failing : IOException in TaskRunner (Error Code :134) >> Reply-To: [email protected] >> >> Hi all, >> >> I am facing a problem with the TaskRunner. I have a small hadoop cluster in >> the fully distributed mode. However when I submit a job, the job never seems >> to proceed beyond the "map 0% reduce 0%" stage. Soon after I get this error: >> >> java.io.IOException: Task process exit with nonzero status of 134. at >> org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:418) >> >> When I googled this issue, I found this link >> http://markmail.org/message/lvefqbcboaqzfazt but did not completely >> understand the issue. The cluster, in this same configuration, was working >> fine a few days back. So, I am confused as to what could have changed to >> cause this error. >> >> Have any of you faced similar problems too? I would be really grateful if >> you could let me know if I am missing something very obvious. >> >> Thanks a lot! >> >> Regards, >> Krishna. >> >
