hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ka...@apache.org
Subject hadoop git commit: YARN-4569. Remove incorrect part of maxResources in FairScheduler documentation. (Ray Chiang via kasha) (cherry picked from commit a0c95b5fc4c90ee3383619156619a66dfba889f7)
Date Thu, 18 Feb 2016 02:58:06 GMT
Repository: hadoop
Updated Branches:
  refs/heads/branch-2 33c198859 -> 25c2597f9


YARN-4569. Remove incorrect part of maxResources in FairScheduler documentation. (Ray Chiang
via kasha)
(cherry picked from commit a0c95b5fc4c90ee3383619156619a66dfba889f7)


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

Branch: refs/heads/branch-2
Commit: 25c2597f9cfb7ca5463ba0e25c7178dd2cfe68b9
Parents: 33c1988
Author: Karthik Kambatla <kasha@apache.org>
Authored: Wed Feb 17 18:36:12 2016 -0800
Committer: Karthik Kambatla <kasha@apache.org>
Committed: Wed Feb 17 18:43:41 2016 -0800

----------------------------------------------------------------------
 hadoop-yarn-project/CHANGES.txt                                   | 3 +++
 .../hadoop-yarn-site/src/site/markdown/FairScheduler.md           | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/25c2597f/hadoop-yarn-project/CHANGES.txt
----------------------------------------------------------------------
diff --git a/hadoop-yarn-project/CHANGES.txt b/hadoop-yarn-project/CHANGES.txt
index 1f36d62..50c913a 100644
--- a/hadoop-yarn-project/CHANGES.txt
+++ b/hadoop-yarn-project/CHANGES.txt
@@ -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

http://git-wip-us.apache.org/repos/asf/hadoop/blob/25c2597f/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/FairScheduler.md
----------------------------------------------------------------------
diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/FairScheduler.md
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/FairScheduler.md
index 01fad34..55293b7 100644
--- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/FairScheduler.md
+++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/FairScheduler.md
@@ -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
 


Mime
View raw message