hadoop-mapreduce-issues mailing list archives

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

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

Vinod Kumar Vavilapalli updated MAPREDUCE-3312:
-----------------------------------------------

    Target Version/s: 0.23.0, 0.24.0  (was: 0.24.0, 0.23.0)
              Status: Open  (was: Patch Available)

bq. Ideally I would also like to make ContainerLauncherImpl safe to have containers launched
and cleaned up in any order,
I am +1 to that. Cleaner than the wait state in TaskAttemptImpl.

MAPREDUCE-3333 is in. but MAPREDUCE-3355 also touches the same part of the code. I am debugging
MAPREDUCE-3402, which may also lurk around the same locality.

If this isn't critical, I'd propose holding off on this one. Once the above issues are completel,
we can do the 'ideal' fix you suggested above. okay?

Thanks.
                
> 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

        

Mime
View raw message