You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/01/02 22:43:27 UTC

[jira] Commented: (HADOOP-846) Progress report is not sent during the intermediate sorts in the map phase

    [ http://issues.apache.org/jira/browse/HADOOP-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461840 ] 

Owen O'Malley commented on HADOOP-846:
--------------------------------------

The status thread is not cleaned up if the merge throws an exception. I think it should probably look like:

try {
  runner.run(...);
  ... merge code ...
} finally {
  in.close();
  collector.close();
  sortProgress.interrupt();
}

so that if run() throws, the merge code won't run. But if the merge code throws then the cleanup is still done.



> Progress report is not sent during the intermediate sorts in the map phase
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-846
>                 URL: http://issues.apache.org/jira/browse/HADOOP-846
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Devaraj Das
>         Assigned To: Devaraj Das
>         Attachments: 846-correct.patch, 846.patch
>
>
> Have seen tasks getting lost at the TaskTracker's end due to MapTask's progress not getting reported for a long time (the configured timeout). The progress report is currently not sent in the intermediate sort phases in the MapTask. But, if for some reason, the sort takes a long time, the TaskTracker might kill the task.

-- 
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