Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.7.6
-
None
-
None
Description
In my cluster, I used label scheduling, and I found that it caused the vcore of the cluster to be incorrect
capacity-scheduler.xml
<configuration> <property> <name>yarn.scheduler.capacity.root.queues</name> <value>support</value> </property> <property> <name>yarn.scheduler.capacity.root.support.capacity</name> <value>100</value> </property> <property> <name>yarn.scheduler.capacity.root.support.accessible-node-labels</name> <value>test1</value> </property> <property> <name>yarn.scheduler.capacity.root.support.accessible-node-labels.test1.capacity</name> <value>100</value> </property> <property> <name>yarn.scheduler.capacity.root.accessible-node-labels.test1.capacity</name> <value>100</value> </property> </configuration>