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

There is a heavy bug in FSLeafQueue#amResourceUsage which will let the fair scheduler not assign container to the queue

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.7.2
    • Fix Version/s: None
    • Component/s: fairscheduler
    • Labels:
      None
    • Target Version/s:

      Description

      There are over three thousand nodes in my hadoop production cluster, and we use fair schedule as my scheduler.
      Though there are many free resource in my resource manager´╝î but there are 46 applications pending.
      Those applications can not run after several hours, and in the end I have to stop them.

      I reproduce the scene in my test environment, and I find a bug in FSLeafQueue.
      In a extreme scenario it will let the FSLeafQueue#amResourceUsage greater than itself.
      When fair scheduler try to assign container to a application attempt, it will do as follow check:


      Because the value of FSLeafQueue#amResourceUsage is invalid, it will greater then it real value.
      So when the value of amResourceUsage greater than the value of Resources.multiply(getFairShare(), maxAMShare) ,
      and the FSLeafQueue#canRunAppAM function will return false which will let the fair scheduler not assign container
      to the FSAppAttempt.
      In this scenario´╝î all the application attempt will pending and never get any resource.

      I find the reason why so many applications in my leaf queue is pending. I will describe it as follow:

      When fair scheduler first assign a container to the application attempt, it will do something as blow:

      When fair scheduler remove the application attempt from the leaf queue, it will do something as blow:

      But when application attempt unregister itself, and all the container in the SchedulerApplicationAttempt#liveContainers
      are complete. There is a APP_ATTEMPT_REMOVED event will send to fair scheduler, but it is asynchronous.
      Before the application attempt is removed from FSLeafQueue, and there are pending request in FSAppAttempt.
      The fair scheduler will assign container to the FSAppAttempt, because the size of the liveContainers will equals to
      1.
      So the FSLeafQueue will add to container resource to the FSLeafQueue#amResourceUsage, it will
      let the value of amResourceUsage greater then itself.
      In the end, the value of FSLeafQueue#amResourceUsage is preety large although there is no application
      it the queue.
      When new application come, and the value of FSLeafQueue#amResourceUsage greater than the value
      of Resources.multiply(getFairShare(), maxAMShare), it will let the scheduler never assign container to
      the queue.
      All of the applications in the queue will always pending.

        Attachments

        1. screenshot-5.png
          16 kB
          YunFan Zhou
        2. screenshot-4.png
          12 kB
          YunFan Zhou
        3. screenshot-3.png
          52 kB
          YunFan Zhou
        4. screenshot-2.png
          28 kB
          YunFan Zhou
        5. screenshot-1.png
          75 kB
          YunFan Zhou

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              daemon YunFan Zhou
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: