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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-beta1
• Component/s: yarn
• Target Version/s: 2.9.0, 3.0.0-beta1
• Assignee: Wangda Tan
• Reporter: Sumana Sathish
• Created: 11/Sep/17 21:12
• Updated: 13/Sep/17 16:37
• Resolved: 13/Sep/17 00:06

Description

Found an issue:

When DefaultContainerCalculator is enabled and opportunistic container allocation is disabled. It is possible that for a NM:

 
Σ(allocated-container.vcores) > nm.configured-vores. 

When this happens, ContainerScheduler will report errors like:

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.