hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3312) Make MR AM not send a stopContainer w/o corresponding start container
Date Tue, 08 Nov 2011 22:15:52 GMT

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

Robert Joseph Evans updated MAPREDUCE-3312:

    Attachment: MR-3312.txt

This patch adds in a new state to TaskAttemptImpl.  The state is triggered if a TA_KILL is
received before the result of the CONTAINER_LAUNCH is known.  It will not issue the CONTAINER_CLEANUP
event until the the result of the CONTAINER_LAUNCH is known.  I chose TaskAttemptImpl because
it is tied 1 to 1 to a container, and in the current code it is the only place to launch or
cleanup a container.  

Ideally I would also like to make ContainerLauncherImpl safe to have containers launched and
cleaned up in any order, but MAPREDUCE-3333 is possibly going to touch the same code, and
because changes to truly make it safe would require significant changes I thought it best
to hold off on it.  If that is something that you want I have the beginnings of a patch for
it that I could also add in fairly quickly.
> Make MR AM not send a stopContainer w/o corresponding start container
> ---------------------------------------------------------------------
>                 Key: MAPREDUCE-3312
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3312
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>             Fix For: 0.23.1
>         Attachments: MR-3312.txt
> This is a follow on to MAPREDUCE-3274.  It is possible, although rare, for the MR AM
to send a stop container before it sends a start container.  This needs to stop that from
happening.  If a stop is found first it should prevent the start from being sent.  It tries
to do this, but only if the stop is currently pending.

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


View raw message