[ 
https://issues.apache.org/jira/browse/YARN-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321860#comment-16321860
 ] 

Akira Ajisaka commented on YARN-7736:
-------------------------------------

{noformat}
*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).
4. The AMRMProxy can enforce load-balancing / overflow policies.
{noformat}
Blank line should be inserted as well.

> Fix itemization in YARN federation document
> -------------------------------------------
>
>                 Key: YARN-7736
>                 URL: https://issues.apache.org/jira/browse/YARN-7736
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Akira Ajisaka
>            Priority: Minor
>              Labels: newbie
>
> https://hadoop.apache.org/docs/r3.0.0/hadoop-yarn/hadoop-yarn-site/Federation.html
> {noformat}
> 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.
> {noformat}
> Blank line should be inserted before itemization to render correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to