[
https://issues.apache.org/jira/browse/YARN-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436893#comment-16436893
]
Hudson commented on YARN-8153:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13990 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13990/])
YARN-8153. Guaranteed containers always stay in SCHEDULED on NM after (wwei:
rev 226bedc0239ba23f3ca0c40dac6aab3777d3ada6)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/scheduler/ContainerScheduler.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/TestContainerManagerRecovery.java
> Guaranteed containers always stay in SCHEDULED on NM after restart
> ------------------------------------------------------------------
>
> Key: YARN-8153
> URL: https://issues.apache.org/jira/browse/YARN-8153
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Major
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8153.001.patch, YARN-8153.002.patch
>
>
> When nm recovery is enabled, after NM restart, some containers always stay in
> SCHEDULED because of no sufficient resources.
> The root cause is that utilizationTracker.addContainerResources has been
> called twice when restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
