[
https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132466#comment-15132466
]
MENG DING commented on YARN-4138:
---------------------------------
Hi, [~jianhe]
I think with a bit of explanation this won't cause confusion. The key message
here is that if a user issues two increase requests in a row, but does not use
the latest token eventually, we consider this a user/app error, because we
don't really understand what the user wants. From Resource Manager's
perspective, at any time, a {{ContainerAllocationExpirer}} can only track one
increase allocation. If two consecutive increase allocations are made, the
second allocation expiration info overwrites the first, which effectively
*cancels* the first allocation.
Let me know if you have further concerns.
> 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, YARN-4138.4.patch,
> YARN-4138.5.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)
