[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
MENG DING updated YARN-4138: ---------------------------- Attachment: YARN-4138.6.patch Attaching a new patch that updates {{lastConfirmedResource}} based on NM reported increased containers. Since the {{containerIncreasedOnNode}} function updates {{lastConfirmedResource}}, we will guard the content with a queue lock, but will drop the cs lock (this is consistent with other functions like {{rollbackContainerResource}}, {{updateIncreaseRequests}} and {{decreaseContainer}}). > 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, YARN-4138.6.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)