[
https://issues.apache.org/jira/browse/YARN-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079416#comment-16079416
]
Giovanni Matteo Fumarola commented on YARN-5412:
------------------------------------------------
Attached a proto version.
Some considerations:
* NodeIDsInfo contained a bug - fixed in this patch.
* LabelsToNodesInfo missed a constructor - fixed in this patch.
* I created in TestRouterWebServicesREST something similar to a
MiniYarnCluster. I am really curious to see what Jenkins acts with this.
* Some Javadoc are missing - I will add them in v1.
* it may contains some Yetus warnings - I will fix them in v1.
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
