[ https://issues.apache.org/jira/browse/YARN-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081267#comment-15081267 ]
MENG DING commented on YARN-4528: --------------------------------- Hi, [~sandflee] I am not quite sure about the benefit of directly decreasing resource in NM (point #2 in your comment). The targetResource is already being persisted in NM state store for NM recovery, and RM does not need to check the status of the NM decrease anyway. {code} // Persist container resource change for recovery this.context.getNMStateStore().storeContainerResourceChanged( containerId, targetResource); {code} > decreaseContainer Message maybe lost if NM restart > -------------------------------------------------- > > Key: YARN-4528 > URL: https://issues.apache.org/jira/browse/YARN-4528 > Project: Hadoop YARN > Issue Type: Bug > Reporter: sandflee > Attachments: YARN-4528.01.patch > > > we may pending the container decrease msg util next heartbeat. or checks the > resource with rmContainer when node register. -- This message was sent by Atlassian JIRA (v6.3.4#6332)