TaskTracker seems to hold onto the assigned task for a long while before
launching it
-------------------------------------------------------------------------------------
Key: HADOOP-5130
URL: https://issues.apache.org/jira/browse/HADOOP-5130
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.20.0
Reporter: Arun C Murthy
Priority: Critical
I saw atleast a couple of instances where the task assigned to the TaskTracker
is launched several minutes after the receipt of the LaunchTaskAction:
{noformat}
2009-01-27 13:55:53,402 INFO org.apache.hadoop.mapred.TaskTracker:
LaunchTaskAction (registerTask): attempt_200901270818_0006_m_000602_0
2009-01-27 13:55:55,129 INFO org.apache.hadoop.mapred.TaskTracker: Trying to
launch : attempt_200901270818_0006_m_000602_0
2009-01-27 13:55:55,129 INFO org.apache.hadoop.mapred.TaskTracker: In
TaskLauncher, current free slots : 2 and trying to launch
attempt_200901270818_0006_m_000602_0
2009-01-27 14:04:17,744 INFO org.apache.hadoop.mapred.TaskTracker: JVM with ID:
jvm_200901270818_0006_m_176495965 given task:
attempt_200901270818_0006_m_000602_0
2009-01-27 14:04:24,020 INFO org.apache.hadoop.mapred.TaskTracker:
attempt_200901270818_0006_m_000602_0 1.0%
2009-01-27 14:04:27,023 INFO org.apache.hadoop.mapred.TaskTracker:
attempt_200901270818_0006_m_000602_0 1.0%
2009-01-27 14:04:30,026 INFO org.apache.hadoop.mapred.TaskTracker:
attempt_200901270818_0006_m_000602_0 1.0%
2009-01-27 14:04:30,362 INFO org.apache.hadoop.mapred.TaskTracker:
attempt_200901270818_0006_m_000602_0 1.0%
2009-01-27 14:04:30,362 INFO org.apache.hadoop.mapred.TaskTracker: Task
attempt_200901270818_0006_m_000602_0 is done.
2009-01-27 14:04:30,362 INFO org.apache.hadoop.mapred.TaskTracker: reported
output size for attempt_200901270818_0006_m_000602_0 was 0
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
