Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-7185

ContainerScheduler should only look at availableResource for GUARANTEED containers when OPPORTUNISTIC container queuing is enabled.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0, 3.0.0-beta1
    • Component/s: yarn
    • Labels:
      None

      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.

        Attachments

        1. YARN-7185.001.patch
          1 kB
          Wangda Tan
        2. YARN-7185.002.patch
          10 kB
          Wangda Tan
        3. YARN-7185.003.patch
          11 kB
          Wangda Tan

          Activity

            People

            • Assignee:
              wangda Wangda Tan
              Reporter:
              ssathish@hortonworks.com Sumana Sathish
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: