[
https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123692#comment-17123692
]
Xiaoqiao He commented on HADOOP-16254:
--------------------------------------
Thanks [~zhengchenyu] and [~John Smith] for your comments and sorry for late
response.
About `safeguard`, I think we should reinforce it using superuser/ugi or
configuration to avoid security vulnerability. I am not sure if it could
resolve the issue [~daryn] mentioned above.
{quote}Proxy address should be in rpc header not connection header, since one
connection can forward multiple clients' ip.{quote}
Sorry don't get it. Do you mean one connection from Router to NameNode could
proxy different client requests? If that, we could set to null after handler
has processed RPC request at Router. The next RPC should set another one
because it is thread-local, and one handler could not process different RPC
request at the same time IMO. Welcome any suggestions and discussions.
> 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]
