You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2011/09/24 03:15:26 UTC
[jira] [Created] (MAPREDUCE-3084) race when KILL_CONTAINER is
received for a LOCALIZED container
race when KILL_CONTAINER is received for a LOCALIZED container
--------------------------------------------------------------
Key: MAPREDUCE-3084
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3084
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Affects Versions: 0.23.0
Reporter: Siddharth Seth
Depending on when ContainersLaunch starts a container, {{KILL_CONTAINER}} when container state is {{LOCALIZED}} ({{LAUNCH_CONTAINER}} event already sent) can end up generating a {{CONTAINER_LAUNCHED}} event - which isn't handled by ContainerState: {{KILLING}}. Also, the launched container won't be killed since {{CLEANUP_CONTAINER}} would have already been processed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-3084) race when KILL_CONTAINER is
received for a LOCALIZED container
Posted by "Hitesh Shah (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hitesh Shah resolved MAPREDUCE-3084.
------------------------------------
Resolution: Duplicate
Fix Version/s: 0.23.0
Target Version/s: 0.23.0
Being addressed as part of MR-3240.
> race when KILL_CONTAINER is received for a LOCALIZED container
> --------------------------------------------------------------
>
> Key: MAPREDUCE-3084
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3084
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Assignee: Hitesh Shah
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MR-3084.1.patch, MR-3084.wip.patch
>
>
> Depending on when ContainersLaunch starts a container, {{KILL_CONTAINER}} when container state is {{LOCALIZED}} ({{LAUNCH_CONTAINER}} event already sent) can end up generating a {{CONTAINER_LAUNCHED}} event - which isn't handled by ContainerState: {{KILLING}}. Also, the launched container won't be killed since {{CLEANUP_CONTAINER}} would have already been processed.
--
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