MENG DING commented on YARN-4138:

Hi, [~sandflee]

Not sure if I fully understand your question. If resource is successfully 
increased in NM, NM will report the increase to RM in the next heartbeat, so 
there will be no token expiration.

For token expiration to occur, the AM needs to acquire the increase token, and 
to NOT call the NMClient.increaseContainerResource API. When RM rolls back the 
resource allocation (implemented in this patch), it follows the same logic of 
decrease resource allocation. When that is done, the AM should get a 
notification from the heartbeat response for resource decrease.

> 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
> 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

Reply via email to