Brandon Scheller created YARN-9515:
--------------------------------------
Summary: Non-exclusive labels do not respect
user-limit-factor/max-capacity
Key: YARN-9515
URL: https://issues.apache.org/jira/browse/YARN-9515
Project: Hadoop YARN
Issue Type: Bug
Components: capacity scheduler
Affects Versions: 2.8.5
Reporter: Brandon Scheller
When using a cluster with non-exclusive labels. Queues will only respect
user-limit-factor for allocations to the default partition. Non-exclusive label
allocations will not consider these factors allowing the labeled partitions
capacity to be completely used up.
To reproduce this, consider this example.
Cluster contains 1 non-exclusive nodelabel: *APPMASTER*
"test" queue has access to all labels: *
"test" queue has capacity/max-capacity: 20
"test" queue has user-limit-factor: 0.1
Job is submitted to "test" queue with label: *APPMASTER* only on its appMaster
container request, and no-label for all other containers.
user-limit-factor and capacity will not be respected for the job on allocations
to the *APPMASTER* partition causing the single job to attempt to use the
entire capacity of the *APPMASTER* partition through non-exclusive allocations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
