TaoYang526 commented on a change in pull request #3389:
URL: https://github.com/apache/hadoop/pull/3389#discussion_r703134626
##########
File path:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
##########
@@ -125,8 +125,8 @@ 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, providing elasticity. |
| `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 submitted applications to a queue, no single
user can use more than 50% of the queue resources. If a third user submits an
application, no single user can use more than 33% of the queue resources. With
4 or more users, no user can use more than 25% of the queues resources. A value
of 100 implies no user limits are imposed. The default is 100. Value is
specified as a integer. |
-| `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 lower maximum resources. Setting this to -1 will
disable the feature. Value is specified as a float. Note: using the flexible
auto queue creation
(yarn.scheduler.capacity.\<queue-path\>.auto-queue-creation-v2) with weights
will automatically set this property to -1, as the dynamic queues will be
created with the hardcoded weight of 1 and in idle cluster scenarios they
should be able to use more resources than calculated. |
+| `yarn.scheduler.capacity.minimum-user-limit-percent` /
`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 submitted applications to a queue, no single
user can use more than 50% of the queue resources. If a third user submits an
application, no single user can use more than 33% of the queue resources. With
4 or more users, no user can use more than 25% of the queues resources. A value
of 100 implies no user limits are imposed. The default is 100. This can be set
for all queues with `yarn.scheduler.capacity.minimum-user-limit-percent` and
can also be
overridden on a per queue basis by setting
`yarn.scheduler.capacity.<queue-path>.minimum-user-limit-percent`. Value is
specified as a integer. |
Review comment:
"The default is 100. Value is specified as a integer." these two clauses
should be put together and "a integer" should be corrected as "an integer".
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
