[YARN-6440] re-visit handling QUEUE-STOP process

• Type: Sub-task
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Component/s: capacity scheduler
• Assignee: Xuan Gong
• Reporter: Xuan Gong
• Created: 04/Apr/17 22:35
• Updated: 05/Apr/17 00:19

Description

Currently, when we stop the parent queue, we would do the following:
1) check the number of active applications. If there is no active application, we would mark the queue state as STOPPED. Otherwise, we mark the queue state as DRAIN, and wait for all the active applications finish.
2) Do the same step for all its children.

So, in current process, we always change the state for parent queue first which will not work in some scenarios, such as the reservation system. In the reservation system, the plan queue will not have any active applications immediately at the beginning. So, when we stop the queue, it would change the queue state into STOPPED immediately which could cause problem.

Issue Links

• is depended upon by: YARN-6431 make DELETE/STOP/CONVERT queues work in reservation system