[
https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534607#comment-16534607
]
Zian Chen commented on YARN-8496:
---------------------------------
[~tangshangwen] , thanks for raising up this issue. This allocation is
basically a multiple resource allocation which uses DRC when calculating the
amount of resource we allocate for each container. When we calculate if the
node has the available resource to do more allocation or not, we pick the
dominant resource and do the calculation. This may cause dominant resource
still have available but some other resource is already not enough to do the
allocation.
I think we need to fix this.
[~sunilg] , could you share thoughts on this?
> The capacity scheduler uses label to cause vcore to be incorrect
> ----------------------------------------------------------------
>
> Key: YARN-8496
> URL: https://issues.apache.org/jira/browse/YARN-8496
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Affects Versions: 2.7.6
> Reporter: tangshangwen
> Assignee: tangshangwen
> Priority: Major
> Attachments: yarn-bug.png
>
>
> In my cluster, I used label scheduling, and I found that it caused the vcore
> of the cluster to be incorrect
>
> capacity-scheduler.xml
>
> {code:java}
> <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>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
