hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires
Date Fri, 25 Dec 2015 07:43:49 GMT

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

sandflee commented on YARN-4138:

Hi, [~mding], sorry for the late reply, 
1, If AM send tokenA succ to NM, and before NM send containerIncreased msg to RM, AM request
resource from 2G -> 4G, get tokenB but never used,  after expire,  RM asks AM to rollback
to 1G, seems not the proper action.  seems [~jianhe] has the same concern. 
1. A container is using 2G
2. AM requests to increase it from 2G --> 8G, and scheduler allocates it and issues token
to AM
3. AM never uses the token, but requests to decrease the container from 8G --> 6G, and
scheduler goes ahead and decrease the resource to 6G, and also removes the container from
allocation expirer
4. RM notifies NM to decrease resource to 6G, but since NM is still using 2G, the decrease
message is ignored by NM
5. Now the container has 6G allocation in RM, but 2G allocation in NM.
in 4, could we send a set msg to NM instead of a decrease msg ?

2, there are race conditions between AM get a new  token and send another resource change
request, I opened a new issues to discuss this (YARN-4495)

> Roll back container resource allocation after resource increase token expires
> -----------------------------------------------------------------------------
>                 Key: YARN-4138
>                 URL: https://issues.apache.org/jira/browse/YARN-4138
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, nodemanager, resourcemanager
>            Reporter: MENG DING
>            Assignee: MENG DING
>         Attachments: YARN-4138-YARN-1197.1.patch, YARN-4138-YARN-1197.2.patch, YARN-4138.3.patch
> In YARN-1651, after container resource increase token expires, the running container
is killed.
> This ticket will change the behavior such that when a container resource increase token
expires, the resource allocation of the container will be reverted back to the value before
the increase.

This message was sent by Atlassian JIRA

View raw message