Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 12 Jul 2017 23:26:00 +0000 (UTC)
From: "Carlo Curino (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12991306.1469063477000.234197.1499901960178@Atlassian.JIRA>
In-Reply-To: <JIRA.12991306.1469063477000@Atlassian.JIRA>
References: <JIRA.12991306.1469063477000@Atlassian.JIRA> <JIRA.12991306.1469063477301@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-5412) Create a proxy chain for
 ResourceManager REST API in the Router
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 12 Jul 2017 23:44:32 -0000


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

Carlo Curino commented on YARN-5412:
------------------------------------

[~giovanni.fumarola], per our offline discussion:
You can probably fix the tests issues by:
# add a {{capacity-scheduler.xml}} to test/resources, 
# fix the {{yarn-default.xml}} (mistakenly setting rm.webaddress instead of router.webaddress), 
# add timeouts to the tests, so it timeouts locally and invokes shutdown, avoiding other tests to fail due to binding issues (more local errors help)

Also completing a first pass on the review:
# {{TestRouterWebServices}} remove LOG.info that are redundant to asserts
# {{TestRouterWebServicesREST}} factor out code in setup to a {{isWebAppRunning}} generic method (with a path in input)
# {{TestRouterWebServicesREST}} factor out all the invocations to something like {{private List<T> performTest(Path, T.class)}}, the return list allows you to add specific size checks outside where appropriate.


> Create a proxy chain for ResourceManager REST API in the Router
> ---------------------------------------------------------------
>
>                 Key: YARN-5412
>                 URL: https://issues.apache.org/jira/browse/YARN-5412
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Giovanni Matteo Fumarola
>         Attachments: YARN-5412-YARN-2915.1.patch, YARN-5412-YARN-2915.2.patch, YARN-5412-YARN-2915.proto.patch
>
>
> 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 REST 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.4.14#64029)

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