Rohith Sharma K S created YARN-4862: ---------------------------------------
Summary: Handle duplicated completed containers in RMNodeImpl Key: YARN-4862 URL: https://issues.apache.org/jira/browse/YARN-4862 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Reporter: Rohith Sharma K S Assignee: Rohith Sharma K S As per [comment|https://issues.apache.org/jira/browse/YARN-4852?focusedCommentId=15209689&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15209689] from [~sharadag], there should be safe guard for duplicated container status in RMNodeImpl before creating UpdatedContainerInfo. Or else in heavily loaded cluster, if any duplicated container are sent to RM(may be bug in NM also), RM should not create UpdatedContainerInfo for duplicated containers. This is an optimization for issue kind YARN-4852 -- This message was sent by Atlassian JIRA (v6.3.4#6332)