hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wan...@apache.org
Subject hadoop git commit: YARN-7628. [Documentation] Documenting the ability to disable elasticity at Capacity Scheduler's sub queues. (Zian Chen via wangda)
Date Wed, 24 Jan 2018 23:31:42 GMT
Repository: hadoop
Updated Branches:
  refs/heads/trunk 0c559b278 -> 051ad9d63


YARN-7628. [Documentation] Documenting the ability to disable elasticity at Capacity Scheduler's
sub queues. (Zian Chen via wangda)

Change-Id: I5c37df1c5bee9e3a78379775ef307ef94506ebc4


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/051ad9d6
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/051ad9d6
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/051ad9d6

Branch: refs/heads/trunk
Commit: 051ad9d63f41ae98be728a7cdbdad9b072316318
Parents: 0c559b2
Author: Wangda Tan <wangda@apache.org>
Authored: Thu Jan 25 07:24:57 2018 +0800
Committer: Wangda Tan <wangda@apache.org>
Committed: Thu Jan 25 07:24:57 2018 +0800

----------------------------------------------------------------------
 .../hadoop-yarn-site/src/site/markdown/CapacityScheduler.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/051ad9d6/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
----------------------------------------------------------------------
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 2598997..87cfd39 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
@@ -123,7 +123,7 @@ Configuration
 | Property | Description |
 |:---- |:---- |
 | `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. Defaults to -1 which disables it. |
+| `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` | 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>.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. |


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


Mime
View raw message