[jira] [Commented] (YARN-7185) ContainerScheduler should only look at availableResource for GUARANTEED containers when OPPORTUNISTIC container queuing is enabled.

2017-09-13 Thread Wangda Tan (JIRA) 

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

Wangda Tan commented on YARN-7185:
--

Thanks [~asuresh] for review and commit! 

> ContainerScheduler should only look at availableResource for GUARANTEED 
> containers when OPPORTUNISTIC container queuing is enabled.
> ---
>
> Key: YARN-7185
> URL: https://issues.apache.org/jira/browse/YARN-7185
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn
>Reporter: Sumana Sathish
>Assignee: Tan, Wangda
>Priority: Blocker
> Fix For: 2.9.0, 3.0.0-beta1
>
> Attachments: YARN-7185.001.patch, YARN-7185.002.patch, 
> YARN-7185.003.patch
>
>
> Found an issue: 
> When DefaultContainerCalculator is enabled and opportunistic container 
> allocation is disabled. It is possible that for a NM:
> {code} 
> Σ(allocated-container.vcores) > nm.configured-vores. 
> {code} 
> When this happens, ContainerScheduler will report errors like:
> bq. ContainerScheduler 
> (ContainerScheduler.java:pickOpportunisticContainersToKill(458)) - There are 
> no sufficient resources to start guaranteed.
> This will be an incompatible change after 2.8 because before YARN-6706, we 
> can start containers when DefaultContainerCalculator is configured and vcores 
> is overallocated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Commented] (YARN-7185) ContainerScheduler should only look at availableResource for GUARANTEED containers when OPPORTUNISTIC container queuing is enabled.

2017-09-12 Thread Hudson (JIRA) 

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

Hudson commented on YARN-7185:
--

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12855 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/12855/])
YARN-7185. [Addendum patch] Minor javadoc and checkstyle fix. (arun suresh: rev 
a1c398e0dc85e424b45c50a3c3a0a784c04ed737)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/scheduler/TestContainerSchedulerBehaviorCompatibility.java


> ContainerScheduler should only look at availableResource for GUARANTEED 
> containers when OPPORTUNISTIC container queuing is enabled.
> ---
>
> Key: YARN-7185
> URL: https://issues.apache.org/jira/browse/YARN-7185
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn
>Reporter: Sumana Sathish
>Assignee: Tan, Wangda
>Priority: Blocker
> Fix For: 2.9.0, 3.0.0-beta1
>
> Attachments: YARN-7185.001.patch, YARN-7185.002.patch, 
> YARN-7185.003.patch
>
>
> Found an issue: 
> When DefaultContainerCalculator is enabled and opportunistic container 
> allocation is disabled. It is possible that for a NM:
> {code} 
> Σ(allocated-container.vcores) > nm.configured-vores. 
> {code} 
> When this happens, ContainerScheduler will report errors like:
> bq. ContainerScheduler 
> (ContainerScheduler.java:pickOpportunisticContainersToKill(458)) - There are 
> no sufficient resources to start guaranteed.
> This will be an incompatible change after 2.8 because before YARN-6706, we 
> can start containers when DefaultContainerCalculator is configured and vcores 
> is overallocated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Commented] (YARN-7185) ContainerScheduler should only look at availableResource for GUARANTEED containers when OPPORTUNISTIC container queuing is enabled.

2017-09-12 Thread Hudson (JIRA) 

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

Hudson commented on YARN-7185:
--

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12853 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/12853/])
YARN-7185. ContainerScheduler should only look at availableResource for (arun 
suresh: rev 2ae72692fc370267141a1ee55ef372ff62302b54)
* (add) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/scheduler/TestContainerSchedulerBehaviorCompatibility.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/TestContainerManager.java
* (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


> ContainerScheduler should only look at availableResource for GUARANTEED 
> containers when OPPORTUNISTIC container queuing is enabled.
> ---
>
> Key: YARN-7185
> URL: https://issues.apache.org/jira/browse/YARN-7185
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: yarn
>Reporter: Sumana Sathish
>Assignee: Tan, Wangda
>Priority: Blocker
> Attachments: YARN-7185.001.patch, YARN-7185.002.patch, 
> YARN-7185.003.patch
>
>
> Found an issue: 
> When DefaultContainerCalculator is enabled and opportunistic container 
> allocation is disabled. It is possible that for a NM:
> {code} 
> Σ(allocated-container.vcores) > nm.configured-vores. 
> {code} 
> When this happens, ContainerScheduler will report errors like:
> bq. ContainerScheduler 
> (ContainerScheduler.java:pickOpportunisticContainersToKill(458)) - There are 
> no sufficient resources to start guaranteed.
> This will be an incompatible change after 2.8 because before YARN-6706, we 
> can start containers when DefaultContainerCalculator is configured and vcores 
> is overallocated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org