hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chengbing Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2997) NM keeps sending finished containers to RM until app is finished
Date Wed, 31 Dec 2014 02:03:13 GMT

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

Chengbing Liu commented on YARN-2997:

[~kasha] [~jianhe] Thanks for your review. I think NM will call {{getNMContainerStatuses()}}
instead of {{getContainerStatuses()}} upon receiving RESYNC from restarted RM. {{getNMContainerStatuses()}}
remains unchanged and still reports all the completed containers for non-completed apps. The
uploaded patch will let the normal heartbeat (not after receiving RESYNC) send only useful
container status information to RM. So I guess the work-preserving RM restart is not affected.

> 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
>         Attachments: 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

View raw message