[ http://issues.apache.org/jira/browse/HADOOP-639?page=comments#action_12455383 ] Mahadev konar commented on HADOOP-639: --------------------------------------
Arun, I meant ... the following: The jobtracker should send the following two messages: 1) KILL_TASK-- which is per task message... and this one kills any task and cleans it up 2) THe other one I mentioned is the one when the JobTracker decides that a job has finished/failed and wants all the tasktrackers to cleanup. In this case we could just send a jobid and cleanup message from the Jobtracker to tasktracker since we have a mapping of jobID --> TIP_EXECUTED_OR_RUNNING on a tasktracker. So we do not need to send cleanup messages for all tasks at the end of job finish/fail. It is the second one that I was talking about in my previous comments. > task cleanup messages can get lost, causing task trackers to keep tasks > forever > ------------------------------------------------------------------------------- > > Key: HADOOP-639 > URL: http://issues.apache.org/jira/browse/HADOOP-639 > Project: Hadoop > Issue Type: Bug > Components: mapred > Affects Versions: 0.7.2 > Reporter: Owen O'Malley > Assigned To: Arun C Murthy > Attachments: HADOOP-639_1.patch, HADOOP-639_2_20061130.patch, > HADOOP-639_3_20061201.patch > > > If the pollForTaskWithClosedJob call from a job tracker to a task tracker > times out when a job completes, the tasks are never cleaned up. This can > cause the mini m/r cluster to hang on shutdown, but also is a resource leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
