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

Carlo Curino commented on YARN-2884:
------------------------------------

I agree we should give it another name... but the LocalRM is a slightly 
different concept YARN-2885, i.e., it is the logic making distributed 
scheduling decisions. 
The "Proxy" itself is just the mechanics to hijack the connection between 
AM-RM, which we will need for some more work on federating multiple RMs (JIRAs 
coming soon).

Hence the need to call out separately the architectural piece (proxy) and the 
distributed scheduling logic (LocalRM). Any name suggestion?  

> Proxying all AM-RM communications
> ---------------------------------
>
>                 Key: YARN-2884
>                 URL: https://issues.apache.org/jira/browse/YARN-2884
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Carlo Curino
>
> We introduce the notion of an RMProxy, running on each node (or once per 
> rack). Upon start the AM is forced (via tokens and configuration) to direct 
> all its requests to a new services running on the NM that provide a proxy to 
> the central RM. 
> This give us a place to:
> 1) perform distributed scheduling decisions
> 2) throttling mis-behaving AMs
> 3) mask the access to a federation of RMs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to