Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 21 Jul 2016 01:12:20 +0000 (UTC)
From: "Subru Krishnan (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12991307.1469063530000.90170.1469063540442@Atlassian.JIRA>
In-Reply-To: <JIRA.12991307.1469063530000@Atlassian.JIRA>
References: <JIRA.12991307.1469063530000@Atlassian.JIRA> <JIRA.12991307.1469063530120@arcas>
Subject: [jira] [Created] (YARN-5413) Create a proxy chain for
 ResourceManager Admin API in the Router
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 21 Jul 2016 01:12:22 -0000

Subru Krishnan created YARN-5413:
------------------------------------

             Summary: Create a proxy chain for ResourceManager Admin API in the Router
                 Key: YARN-5413
                 URL: https://issues.apache.org/jira/browse/YARN-5413
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Subru Krishnan


As detailed in the proposal in the umbrella JIRA, we are introducing a new component that routes client request to appropriate ResourceManager(s). This JIRA tracks the creation of a proxy for ResourceManager Admin API in the Router. This provides a placeholder for:
1) throttling mis-behaving clients (YARN-1546)
3) mask the access to multiple RMs (YARN-3659)

We are planning to follow the interceptor pattern like we did in YARN-2884 to generalize the approach and have only dynamically coupling for Federation.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org