[
https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415313#comment-17415313
]
Janus Chow edited comment on HADOOP-16254 at 9/15/21, 4:25 AM:
---------------------------------------------------------------
[~hexiaoqiao] [~daryn] For the safety concern, can we add a configuration like
"hadoop.proxyuser.xxx.hosts", maybe "hadoop.proxyAddress.hosts" and the
following policies:
# Router: make sure all requests send by Router have the proxyAddress
# NameNode:
## only requests send by hosts in "hadoop.proxyAddress.hosts" can have the
field of "proxyAddress", or reject the requests.
## the content of "hadoop.proxyAddress.hosts" should be the hosts of Routers.
## NameNode should support dynamic refresh of the configuration in case of
adding/removing Routers.
# Clients:
## Shouldn't set the proxyAddress
## Even the configuration is set, NN should reject the requests since its
connection peer is not in "hadoop.proxyAddress.hosts".
was (Author: symious):
[~hexiaoqiao] [~daryn] For the safety concern, can we add a configuration like
"hadoop.proxyuser.xxx.hosts", maybe "hadoop.proxyAddress.hosts" and the
following policies:
# Router: make sure all requests send by Router have the proxyAddress
# NameNode:
## only requests send by hosts in "hadoop.proxyAddress.hosts" can have the
field of "proxyAddress", or reject the requests.
## the content of "hadoop.proxyAddress.hosts" should be the hosts of Routers.
## NameNode should support dynamic refresh of the configuration in case of
adding/removing Routers.
# Clients:
## Shouldn't set the proxyAddress
## Even the configuration is set, NN should reject the requests since it
connection peer is not in "hadoop.proxyAddress.hosts".
> Add proxy address in IPC connection
> -----------------------------------
>
> Key: HADOOP-16254
> URL: https://issues.apache.org/jira/browse/HADOOP-16254
> Project: Hadoop Common
> Issue Type: New Feature
> Components: ipc
> Reporter: Xiaoqiao He
> Assignee: Xiaoqiao He
> Priority: Major
> Attachments: HADOOP-16254.001.patch, HADOOP-16254.002.patch,
> HADOOP-16254.004.patch
>
>
> In order to support data locality of RBF, we need to add new field about
> client hostname in the RPC headers of Router protocol calls.
> clientHostname represents hostname of client and forward by Router to
> Namenode to support data locality friendly. See more [RBF Data Locality
> Design|https://issues.apache.org/jira/secure/attachment/12965092/RBF%20Data%20Locality%20Design.pdf]
> in HDFS-13248 and [maillist
> vote|http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201904.mbox/%3CCAF3Ajax7hGxvowg4K_HVTZeDqC5H=3bfb7mv5sz5mgvadhv...@mail.gmail.com%3E].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
