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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2012/12/17 20:50:15 UTC

[jira] [Commented] (MAPREDUCE-4880) TaskImpl interprets death of second attempt as RetroactiveKilledTransition even when first attempt succeeds

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

Bikas Saha commented on MAPREDUCE-4880:
---------------------------------------

Could you please confirm that you dont have the code from MAPREDUCE-4607 in your repro? If there is a repro with those fixes then maybe there is some other bug.
                
> TaskImpl interprets death of second attempt as RetroactiveKilledTransition even when first attempt succeeds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4880
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4880
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>
> Consider a reduce task with 2 attempts, one running and one unassigned.  Reduce task attempt 1 succeeds.  This causes reduce task attempt 2 to be killed.  This causes reduce task attempt 2 to issue a T_ATTEMPT_KILLED, which the TaskImpl interprets as a RetroactiveKilledTransition.  As RetroactiveKilledTransitions are supposed to only apply to map events, the TaskImpl errors with "Unexpected event for REDUCE task T_ATTEMPT_KILLED".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira