[
https://issues.apache.org/jira/browse/YARN-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991308#comment-15991308
]
Giovanni Matteo Fumarola commented on YARN-5411:
------------------------------------------------
Thanks [~subru] for the feedbacks.
* Done.
* I opened YARN-6539, I will update in the next patch.
* Done.
* Done.
* Done.
* Done.
* The 2 chains have different objects. Refactoring and Reusing will add
additional complexity to the code and it may reduce the stability. I tested
this code for long time.
* Done.
* There is no a double translating.
* Done.
* I opened YARN-6537 to track this.
* Moved to a yarn-server-common. I add in the pom.xml in nodemanager and router
the test-dependency on it. Right now it has the version dependency, I did not
find a way to avoid it.
* Done.
* I added comments to avoid confusions.
* test1, test2 are the names of UGIs.
> Create a proxy chain for ApplicationClientProtocol in the Router
> ----------------------------------------------------------------
>
> Key: YARN-5411
> URL: https://issues.apache.org/jira/browse/YARN-5411
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Subru Krishnan
> Assignee: Giovanni Matteo Fumarola
> Attachments: YARN-5411-YARN-2915.v1.patch,
> YARN-5411-YARN-2915.v2.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 ApplicationClientProtocol 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
