YARN-7736. Fix itemization in YARN federation document

Signed-off-by: Akira Ajisaka <aajis...@apache.org>


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

Branch: refs/heads/HDFS-7240
Commit: 245751ffdc4229715a0c031f57f20748ed16d8a6
Parents: 1054b48
Author: Sen Zhao <zhao....@zte.com.cn>
Authored: Mon Mar 5 11:22:09 2018 -0800
Committer: Akira Ajisaka <aajis...@apache.org>
Committed: Mon Mar 5 11:54:24 2018 -0800

----------------------------------------------------------------------
 .../hadoop-yarn/hadoop-yarn-site/src/site/markdown/Federation.md   | 2 ++
 1 file changed, 2 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/245751ff/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/Federation.md
----------------------------------------------------------------------
diff --git 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/Federation.md
 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/Federation.md
index 40d46cb..a1d3ab6 100644
--- 
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/Federation.md
+++ 
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/Federation.md
@@ -29,6 +29,7 @@ This architecture can provide very tight enforcement of 
scheduling invariants wi
 Federation is designed as a “layer” atop of existing YARN codebase, with 
limited changes in the core YARN mechanisms.
 
 Assumptions:
+
 * We assume reasonably good connectivity across sub-clusters (e.g., we are not 
looking to federate across DC yet, though future investigations of this are not 
excluded).
 * We rely on HDFS federation (or equivalently scalable DFS solutions) to take 
care of scalability of the store side.
 
@@ -71,6 +72,7 @@ to minimize overhead on the scheduling infrastructure (more 
in section on scalab
 ![Architecture of the AMRMProxy interceptor chain | 
width=800](./images/amrmproxy_architecture.png)
 
 *Role of AMRMProxy*
+
 1. Protect the sub-cluster YARN RMs from misbehaving AMs. The AMRMProxy can 
prevent DDOS attacks by throttling/killing AMs that are asking too many 
resources.
 2. Mask the multiple YARN RMs in the cluster, and can transparently allow the 
AM to span across sub-clusters. All container allocations are done by the YARN 
RM framework that consists of the AMRMProxy fronting the home and other 
sub-cluster RMs.
 3. Intercepts all the requests, thus it can enforce application quotas, which 
would not be enforceable by sub-cluster RM (as each only see a fraction of the 
AM requests).


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

Reply via email to