[ 
https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268546#comment-14268546
 ] 

Jian He commented on YARN-2997:
-------------------------------

ah, I think the problem that container statuses whose application are stopped 
may be lost on NM resync exists before.  thanks for your clarification.  one 
minor comment: {{LinkedHashMap<ContainerId, ContainerStatus>()}},  a regular 
HashMap should be enough instead of a linkedHashMap?

> NM keeps sending finished containers to RM until app is finished
> ----------------------------------------------------------------
>
>                 Key: YARN-2997
>                 URL: https://issues.apache.org/jira/browse/YARN-2997
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: Chengbing Liu
>            Assignee: Chengbing Liu
>         Attachments: YARN-2997.2.patch, YARN-2997.3.patch, YARN-2997.4.patch, 
> YARN-2997.patch
>
>
> We have seen in RM log a lot of
> {quote}
> INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Null container completed...
> {quote}
> It is caused by NM sending completed containers repeatedly until the app is 
> finished. On the RM side, the container is already released, hence 
> {{getRMContainer}} returns null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to