[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134926#comment-15134926 ]
MENG DING commented on YARN-4138: --------------------------------- Hi, [~jianhe] and [~sandflee] After more thoughts, I think we should be able to update last confirmed resource every time we get a report of increased containers from NM, like the following: {code} if (rmContainerResource == nmContainerResource) { lastConfirmedResource = nmContainerResource containerAllocationExpirer.unregister } else if (rmContainerResource < nmContainerResource) { // sandflee's use case lastConfirmedResource = rmContainerResource containerAllocationExpirer.unregister handle(RMNodeDecreaseContainerEvent) } else if (nmContainerResource < rmContainerResource ) { // consecutive increase use case lastConfirmedResource = max(nmContainerResource, lastConfirmedResource ) } {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, 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)