[YARN-7003] DRAINING state of queues is not recovered after RM restart

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0, 3.0.0-alpha4
• Fix Version/s: 3.2.0, 3.1.1, 2.9.2, 3.0.3
• Component/s: capacityscheduler
• Hadoop Flags: Reviewed
• Assignee: Tao Yang
• Reporter: Tao Yang
• Created: 13/Aug/17 02:20
• Updated: 16/May/18 14:57
• Resolved: 11/May/18 03:12

Description

DRAINING state is a temporary state in RM memory, when queue state is set to be STOPPED but there are still some pending or active apps in it, the queue state will be changed to DRAINING instead of STOPPED after refreshing queues. We've encountered the problem that the state of this queue will aways be STOPPED after RM restarted, so that it can be removed at any time and leave some apps in a non-existing queue.
To fix this problem, we could recover DRAINING state in the recovery process of pending/active apps. I will upload a patch with test case later for review.