[YARN-3278] Queue's current-max-limit should be updated when container allocated/released in another queue

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: capacityscheduler, resourcemanager
• Assignee: Wangda Tan
• Reporter: Wangda Tan
• Created: 27/Feb/15 19:51
• Updated: 27/Feb/15 19:52

Description

This is a problem after YARN-2008, queue's current-max-limit (it was called maxAvailCapacity in YARN-2008) will be updated when queue is traversed by scheduler, so application can get headroom based on staled current-max-limit. For example:

      r
     / \
    a   b
   /     \
  a1      b1

   ^       ^
   |       |
   app1    app2

We have above queue structure, two apps in the cluster: app1 in a1, and app2 in b1. If scheduler always travers b1 only, and continously allocate containers in b1, app1's headroom will not get updated.