You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2014/07/03 01:26:24 UTC

[jira] [Updated] (YARN-2249) AM resync may send container release request before container is actually recovered

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

Jian He updated YARN-2249:
--------------------------

    Description: AM resync on RM restart will send outstanding resource requests, container release list etc. back to the new RM. It is possible that RM receives the container release request  before the container is actually recovered.    (was: AM resync on RM restart will send outstanding resource requests, container release list etc. back to the new RM. It is possible that container release request is processed before the container is actually recovered.  )

> AM resync may send container release request before container is actually recovered
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-2249
>                 URL: https://issues.apache.org/jira/browse/YARN-2249
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>
> AM resync on RM restart will send outstanding resource requests, container release list etc. back to the new RM. It is possible that RM receives the container release request  before the container is actually recovered.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)