[jira] [Updated] (YARN-8153) Guaranteed containers always stay in SCHEDULED on NM after restart
[ https://issues.apache.org/jira/browse/YARN-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Wang updated YARN-8153: Attachment: YARN-8153.002.patch > 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 > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8153) Guaranteed containers always stay in SCHEDULED on NM after restart
[ https://issues.apache.org/jira/browse/YARN-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Wang updated YARN-8153: Attachment: YARN-8153.001.patch > 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 > Attachments: YARN-8153.001.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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
