[YARN-2918] Don't fail RM if queue's configured labels are not existed in cluster-node-labels

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.1, 2.8.0, 2.7.1, 3.0.0-alpha1
• Component/s: resourcemanager
• Labels: 2.6.1-candidate
• Hadoop Flags: Reviewed
• Assignee: Wangda Tan
• Reporter: Rohith Sharma K S
• Created: 03/Dec/14 14:46
• Updated: 30/Aug/16 01:29
• Resolved: 08/May/15 00:37

Description

Currently, if admin setup labels on queues <queue-path>.accessible-node-labels = .... And the label is not added to RM, queue's initialization will fail and RM will fail too:

2014-12-03 20:11:50,126 FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting ResourceManager
...
Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, please check.
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.<init>(AbstractCSQueue.java:109)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.<init>(LeafQueue.java:120)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324)
	at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)

This is not a good user experience, we should stop fail RM so that admin can configure queue/labels in following steps:

• Configure queue (with label)
• Start RM
• Add labels to RM
• Submit applications

Now admin has to:

• Configure queue (without label)
• Start RM
• Add labels to RM
• Refresh queue's config (with label)
• Submit applications