hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5280) When expiring a lost launched task, JT doesn't remove the attempt from the taskidToTIPMap.
Date Mon, 23 Feb 2009 10:49:04 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675847#action_12675847
] 

Vinod K V commented on HADOOP-5280:
-----------------------------------

The original circumstances under which this bug was revealed was HADOOP-5285.  With the above
patch, and without patch for HADOOP-5285, the symptom of stuck reducers waiting for output
from already failed tasks doesn't seem to be visible any more.

The patch uploaded prevents tasks from wrongly going from FAILED state to any of UNASSIGNED,
RUNNING, COMMI_PENDING or SUCCEEDED and looks fine.

`ant test` and `ant test-patch` passed successfully on my local machine. +1 overall.

> When expiring a lost launched task, JT doesn't remove the attempt from the taskidToTIPMap.
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5280
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5280
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.20.0
>            Reporter: Vinod K V
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 5280.patch
>
>


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


Mime
View raw message