[
https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071682#comment-15071682
]
MENG DING commented on YARN-4138:
---------------------------------
Hi, [~sandflee]
In your step 3, the container will NOT be removed from allocation expirer.
Please see the following code in the patch:
{code}
+ // Only unregister from the containerAllocationExpirer when target
+ // resource is less than or equal to the last confirmed resource.
+ if (Resources.fitsIn(targetResource, lastConfirmedResource)) {
+ container.lastConfirmedResource = targetResource;
+ container.containerAllocationExpirer.unregister(
+ new AllocationExpirationInfo(event.getContainerId()));
+ }
{code}
> 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
(v6.3.4#6332)
