hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-75) RMContainer should handle a RELEASE event while RUNNING
Date Fri, 31 Aug 2012 23:59:07 GMT

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

Siddharth Seth updated YARN-75:

    Attachment: YARN-75.txt

RMContainer now goes into a KILLED state in this situation. Would COMPLETED be a better state,
since we don't really know the reason for the RELEASE. Does it make sense to differentiate
between KILLED and COMPLETED in RMContainer (both being final states).
> RMContainer should handle a RELEASE event while RUNNING
> -------------------------------------------------------
>                 Key: YARN-75
>                 URL: https://issues.apache.org/jira/browse/YARN-75
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-alpha
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: YARN-75.txt
> An AppMaster can send a container release at any point. Currently this results in an
exception, if this is done while the RM considers the container to be RUNNING.
> The event not being processed correctly also implies that these containers do not show
up in the Completed Container List seen by the AM (AMRMProtocol). MR-3902 depends on this
set being complete. 

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

View raw message