hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-7185) ContainerScheduler should only look at availableResource for GUARANTEED containers when opportunistic scheduling is enabled
Date Mon, 11 Sep 2017 22:23:00 GMT

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

Wangda Tan updated YARN-7185:
-----------------------------
    Description: 
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.

  was:
Application fails to go to FINISHED state or sometimes to RUNNING state.
In the nodemanager, we can see the following warnings 
{Code}
 WARN scheduler.ContainerScheduler (ContainerScheduler.java:pickOpportunisticContainersToKill(458))
- There are no sufficient resources to start guaranteed container_<id> at the moment.
Opportunistic containers are in the process ofbeing killed to make room
{Code}


> ContainerScheduler should only look at availableResource for GUARANTEED containers when
opportunistic scheduling 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
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message