Matt Zytaruk wrote:
I am having this same problem during the reduce phase of fetching, and
am now seeing:
060119 132458 Task task_r_obwceh timed out. Killing.
That is a different problem: a different timeout. This happens when a
task does not report status for too long then it is assumed to be hung.
Will the jobtracker restart this job?
It will retry that task up to three times.
If so, if I change the ipc timeout
in the config, will the tasktracker read in the new value when the job
restarts?
The ipc timeout is not the relevant timeout. The task timeout is what's
involved here. And, no, at present I think the tasktracker only reads
this when it is started, not per job.
Doug
