hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-3985) handleTaskAttemptCompletion() called twice for same task attempt from KillWaitAttemptKilledTransition & AttemptKilledTransition
Date Wed, 07 Mar 2012 23:16:58 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bikas Saha resolved MAPREDUCE-3985.
-----------------------------------

    Resolution: Not A Problem

Not an issue. I got confused between AttemptKilledTransition and KillTransition.
                
> handleTaskAttemptCompletion() called twice for same task attempt from KillWaitAttemptKilledTransition
& AttemptKilledTransition
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3985
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3985
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 0.23.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>             Fix For: 0.23.2
>
>
> TaskImpl state changes to KILL_WAIT after an AttemptKilledTransition. When the attempt
reports that it has actually been killed then KILL_WAIT transitions out via the KillWaitAttemptKilledTransition.
Both these transitions send task completion events to Job with the same Killed state.
> The handler simply puts them in a list and so nothing bad has happened till now.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message