You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Subru Krishnan (JIRA)" <ji...@apache.org> on 2015/08/26 01:45:46 UTC

[jira] [Assigned] (YARN-4083) Add a discovery mechanism for the scheduler addresss

     [ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Subru Krishnan reassigned YARN-4083:
------------------------------------

    Assignee: Subru Krishnan  (was: Kishore Chaliparambil)

> Add a discovery mechanism for the scheduler addresss
> ----------------------------------------------------
>
>                 Key: YARN-4083
>                 URL: https://issues.apache.org/jira/browse/YARN-4083
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>
> 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)