[YARN-2744] Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.5.1
• Fix Version/s: 2.6.0
• Component/s: capacityscheduler
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Wangda Tan
• Reporter: Sumit Mohanty
• Created: 25/Oct/14 06:51
• Updated: 01/Dec/14 03:11
• Resolved: 07/Nov/14 01:30

Description

Use the following steps:

• Ensure default in-memory storage is configured for labels
• Define some labels and assign nodes to labels (e.g. define two labels and assign both labels to the host on a one host cluster)
• Invoke refreshQueues
• Modify capacity scheduler to create two top level queues and allow access to the labels from both the queues
• Assign appropriate "label + queue" specific capacities
• Restart resource manager

Noticed that RM starts without any issues. The labels are not preserved across restart and thus the capacity-scheduler ends up using labels that are no longer present.

At this point submitting an application to YARN will not succeed as there are no resources available with the labels.