YARN-4569. Remove incorrect part of maxResources in FairScheduler documentation. (Ray Chiang via kasha)

(cherry picked from commit a0c95b5fc4)
This commit is contained in:
Karthik Kambatla 2016-02-17 18:36:12 -08:00
parent 33c1988595
commit 25c2597f9c
2 changed files with 4 additions and 1 deletions

View File

@ -152,6 +152,9 @@ Release 2.9.0 - UNRELEASED
YARN-4684. TestYarnCLI#testGetContainers failing in CN locale.
(Bibin A Chundatt via vvasudev)
YARN-4569. Remove incorrect part of maxResources in FairScheduler
documentation. (Ray Chiang via kasha)
Release 2.8.0 - UNRELEASED
INCOMPATIBLE CHANGES

View File

@ -94,7 +94,7 @@ The allocation file must be in XML format. The format contains five types of ele
* minResources: minimum resources the queue is entitled to, in the form "X mb, Y vcores". For the single-resource fairness policy, the vcores value is ignored. If a queue's minimum share is not satisfied, it will be offered available resources before any other queue under the same parent. Under the single-resource fairness policy, a queue is considered unsatisfied if its memory usage is below its minimum memory share. Under dominant resource fairness, a queue is considered unsatisfied if its usage for its dominant resource with respect to the cluster capacity is below its minimum share for that resource. If multiple queues are unsatisfied in this situation, resources go to the queue with the smallest ratio between relevant resource usage and minimum. Note that it is possible that a queue that is below its minimum may not immediately get up to its minimum when it submits an application, because already-running jobs may be using those resources.
* maxResources: maximum resources a queue is allowed, in the form "X mb, Y vcores". For the single-resource fairness policy, the vcores value is ignored. A queue will never be assigned a container that would put its aggregate usage over this limit.
* maxResources: maximum resources a queue is allowed, in the form "X mb, Y vcores". A queue will never be assigned a container that would put its aggregate usage over this limit.
* maxRunningApps: limit the number of apps from the queue to run at once