You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2017/09/11 22:33:00 UTC

[jira] [Commented] (YARN-7185) ContainerScheduler should only look at availableResource for GUARANTEED containers when opportunistic scheduling is enabled

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

Wangda Tan commented on YARN-7185:
----------------------------------

A simple fix for this issue in my mind is only do available resource check when max opportunistic queue len configured to > 0. Please see attached ver.001 patch.

> 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
>         Attachments: YARN-7185.001.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org