[ https://issues.apache.org/jira/browse/YARN-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641084#comment-14641084 ]
Jian He edited comment on YARN-1644 at 7/24/15 9:20 PM: -------------------------------------------------------- bq. if NM fails to send the increasedContainers to RM, Even if NM succeeded to send the increasedContainers to RM, if NM re-registers back with RM before the container size is updated, RM will also recover the container with old resources. The solution I have in mind is that, we do not keep track of extra increasedContainers in NMContext. We always rely on NMContext#containers to send the container status. RM will check container size based on the containerStatus in node heartbeat. was (Author: jianhe): bq. if NM fails to send the increasedContainers to RM, Even if NM succeeded to send the increasedContainers to RM, if NM re-registers back with RM before the container size is updated, RM will also recover the container with old resources. The solution I have in mind is that, we do not keep track of extra increasedContainers in NMContext. We always rely on NMContext#containers to send the container status. RM will re-size container based on the containerStatus in node heartbeat. > RM-NM protocol changes and NodeStatusUpdater implementation to support > container resizing > ----------------------------------------------------------------------------------------- > > Key: YARN-1644 > URL: https://issues.apache.org/jira/browse/YARN-1644 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager > Reporter: Wangda Tan > Assignee: MENG DING > Attachments: YARN-1644-YARN-1197.4.patch, > YARN-1644-YARN-1197.5.patch, YARN-1644.1.patch, YARN-1644.2.patch, > YARN-1644.3.patch, yarn-1644.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)