[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hadoop-commits
Subject:    [hadoop] branch trunk updated: YARN-10609. Update the document for YARN-10531(Be able to disable use
From:       pbacsko () apache ! org
Date:       2021-02-24 19:42:34
Message-ID: 161419575440.4715.5296092505762913859 () gitbox ! apache ! org
[Download RAW message or body]

This is an automated email from the ASF dual-hosted git repository.

pbacsko pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/hadoop.git


The following commit(s) were added to refs/heads/trunk by this push:
     new a89c624  YARN-10609. Update the document for YARN-10531(Be able to disable \
user limit factor for CapacityScheduler Leaf Queue). Contributed by Qi Zhu. a89c624 \
is described below

commit a89c624002fc4fc956f70bd6b641511bee6c2e35
Author: Peter Bacsko <pbacsko@cloudera.com>
AuthorDate: Wed Feb 24 20:41:35 2021 +0100

    YARN-10609. Update the document for YARN-10531(Be able to disable user limit \
                factor for CapacityScheduler Leaf Queue). Contributed by Qi Zhu.
---
 .../hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md \
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
 index e5b23a7..8acf723 100644
--- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
                
+++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
 @@ -126,7 +126,7 @@ Configuration
 | `yarn.scheduler.capacity.<queue-path>.capacity` | Queue *capacity* in percentage \
(%) as a float (e.g. 12.5) OR as absolute resource queue minimum capacity. The sum of \
capacities for all queues, at each level, must be equal to 100. However if absolute \
resource is configured, sum of absolute resources of child queues could be less than \
it's parent absolute resource capacity. Applications in the queue may consume more \
resources than the queue's capacity if there are free resources, provid [...]  | \
`yarn.scheduler.capacity.<queue-path>.maximum-capacity` | Maximum queue capacity in \
percentage (%) as a float OR as absolute resource queue maximum capacity. This limits \
the *elasticity* for applications in the queue. 1) Value is between 0 and 100. 2) \
Admin needs to make sure absolute maximum capacity >= absolute capacity for each \
queue. Also, setting this value to -1 sets maximum capacity to 100%. |  | \
`yarn.scheduler.capacity.<queue-path>.minimum-user-limit-percent` | Each queue \
enforces a limit on the percentage of resources allocated to a user at any given \
time, if there is demand for resources. The user limit can vary between a minimum and \
maximum value. The former (the minimum value) is set to this property value and the \
latter (the maximum value) depends on the number of users who have submitted \
applications. For e.g., suppose the value of this property is 25. If two users have \
                [...]
-| `yarn.scheduler.capacity.<queue-path>.user-limit-factor` | The multiple of the \
queue capacity which can be configured to allow a single user to acquire more \
resources. By default this is set to 1 which ensures that a single user can never \
take more than the queue's configured capacity irrespective of how idle the cluster \
is. Value is specified as a float. | +| \
`yarn.scheduler.capacity.<queue-path>.user-limit-factor` | User limit factor provides \
a way to control the max amount of resources that a single user can consume. It is \
the multiple of the queue's capacity. By default this is set to 1 which ensures that \
a single user can never take more than the queue's configured capacity irrespective \
of how idle the cluster is. Increasing it means a single user can use more than the \
minimum capacity of the cluster, while decreasing it results in lowe [...]  | \
`yarn.scheduler.capacity.<queue-path>.maximum-allocation-mb` | The per queue maximum \
limit of memory to allocate to each container request at the Resource Manager. This \
setting overrides the cluster configuration `yarn.scheduler.maximum-allocation-mb`. \
This value must be smaller than or equal to the cluster maximum. |  | \
`yarn.scheduler.capacity.<queue-path>.maximum-allocation-vcores` | The per queue \
maximum limit of virtual cores to allocate to each container request at the Resource \
Manager. This setting overrides the cluster configuration \
`yarn.scheduler.maximum-allocation-vcores`. This value must be smaller than or equal \
to the cluster maximum. |  | \
`yarn.scheduler.capacity.<queue-path>.user-settings.<user-name>.weight` | This \
floating point value is used when calculating the user limit resource values for \
users in a queue. This value will weight each user more or less than the other users \
in the queue. For example, if user A should receive 50% more resources in a queue \
than users B and C, this property will be set to 1.5 for user A.  Users B and C will \
default to 1.0. |


---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]