[
https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269918#comment-14269918
]
Hudson commented on YARN-2997:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #6833 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/6833/])
YARN-2997. Fixed NodeStatusUpdater to not send alreay-sent completed container
statuses on heartbeat. Contributed by Chengbing Liu (jianhe: rev
cc2a745f7e82c9fa6de03242952347c54c52dccc)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeStatusUpdater.java
* hadoop-yarn-project/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.java
> NM keeps sending already-sent completed containers to RM until containers are
> removed from context
> --------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 2.7.0
>
> Attachments: YARN-2997.2.patch, YARN-2997.3.patch, YARN-2997.4.patch,
> YARN-2997.5.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)
