You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2009/10/15 11:44:31 UTC

[jira] Commented: (MAPREDUCE-1116) Task continues to get localized even though it is marked for killing already

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765986#action_12765986 ] 

Vinod K V commented on MAPREDUCE-1116:
--------------------------------------

This will also delay releasing the slot till localization (for the killed task) finishes.

> Task continues to get localized even though it is marked for killing already
> ----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1116
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1116
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>            Reporter: Vinod K V
>
> Even after the task is marked for killing, because TT doesn't explicitly check for the task state at various stages like downloading job jar, job conf and distributed cache files, it continues to localize the task. This is waste of resources and time and in some cases affects other tasks. Particularly it continues to download distributed cache files and aggravates issues like MAPREDUCE-1098.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.