Here is one more piece in the logs that might be helpful that i noticed
on the namenode-jobtracker.log:
2009-06-26 15:20:29,200 WARN org.apache.hadoop.mapred.JobInProgress:
Running cache for maps missing!! Job details are missing.
2009-06-26 15:20:29,201 WARN org.apache.hadoop.mapred.JobInProgress:
Non-running cache for maps missing!! Job details are missing.
Thanks,
Usman
Hi All,
On one of the test clusters when i try to launch map/reduce job it
fails with the following error.
/
I am getting the following error in my jobtracker.log on the namenode:/
2009-06-26 15:20:12,811 INFO org.apache.hadoop.mapred.JobTracker:
Adding task 'attempt_200906261401_0005_m_000001_0' to tip
task_200906261401_0005_m_000001, for tracker
'tracker_datanode1:localhost/127.0.0.1:33748'
2009-06-26 15:20:14,016 INFO org.apache.hadoop.mapred.TaskInProgress:
Error from attempt_200906261401_0005_m_000001_0: java.io.IOException:
Task process exit with nonzero status of 1.
at org.apache.hadoop.mapred.TaskRunner.runChild(TaskRunner.java:462)
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:403)
/My tasktracker log on datanode1 is reporting the following for the
attempt noted above:
/2009-06-26 15:20:13,449 INFO org.apache.hadoop.mapred.TaskTracker:
LaunchTaskAction: attempt_200906261401_0005_m_000001_0
2009-06-26 15:20:13,700 WARN org.apache.hadoop.mapred.TaskRunner:
attempt_200906261401_0005_m_000001_0 Child Error
java.io.IOException: Task process exit with nonzero status of 1.
at
org.apache.hadoop.mapred.TaskRunner.runChild(TaskRunner.java:462)
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:403)
2009-06-26 15:20:14,656 INFO org.apache.hadoop.mapred.TaskTracker:
LaunchTaskAction: attempt_200906261401_0005_m_000002_0
2009-06-26 15:20:14,811 WARN org.apache.hadoop.mapred.TaskRunner:
attempt_200906261401_0005_m_000002_0 Child Error
java.io.IOException: Task process exit with nonzero status of 1.
at
org.apache.hadoop.mapred.TaskRunner.runChild(TaskRunner.java:462)
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:403)
Seems to be some problem with the Job not being to start on the
datanode(s).
I ran hadoop fsck and the system is healthy. Checked the namenode.log
and no errors are being reported either. These errors happen when i
submit a job to the cluster.
Any clues or comments please?
Thanks,
Usman
/
/
