Hi Doug
I did some more testings using the last svn. Childs still die without any
clear log after a while.
I used two machines through Hadoop, both are datanode and tasktracker and
one is namenode and jobtracker. I started with 2000 seed nodes and it went
fine till 4th cycle, reached about
Still got the same...
I'm not sure if it is relevant to this issue but the call you added to
Fetcher.java:
job.setBoolean(mapred.speculative.execution, false);
Doesn't work. All task trackers still fetch together though I have only
3 sites in the fetchlist.
The task trackers fetch the
Mike Smith wrote:
060219 142408 task_m_grycae Parent died. Exiting task_m_grycae
This means the child process, executing the task, was unable to ping its
parent process (the task tracker).
060219 142408 task_m_grycae Child Error
java.io.IOException: Task process exit with nonzero status.
During fetch all tasktrackers aborting the fetch with:
task_m_b45ma2 Child Error
java.io.IOException: Task process exit with nonzero status.
at
org.apache.hadoop.mapred.TaskRunner.runChild(TaskRunner.java:144)
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:97)
