hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2249) RM may receive container release request on AM resync before container is actually recovered
Date Sun, 20 Jul 2014 23:29:38 GMT

    [ https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068076#comment-14068076
] 

Jian He commented on YARN-2249:
-------------------------------

One possible solution is to have AM always send the whole pending release requests in every
allocate.  The pending release will be decremented once AM receives the completed status of
the released container.
Specifically, changing AMRMClient to send the pendingRelease instead of release in the allocate
method.


> RM may receive container release request on AM resync 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 container release requests back to the
new RM. In the meantime, NMs report the container statuses back to RM to recover the containers.
If RM receives the container release request  before the container is actually recovered in
scheduler, the container won't be released and the release request will be lost.



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

Mime
View raw message