[
https://issues.apache.org/jira/browse/HDFS-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16624498#comment-16624498
]
Fei Hui commented on HDFS-13293:
--------------------------------
[~elgoiri] My idea is that there are two issues, one is that namenode should
log router callercontext which contians real client ip, another is that
resolving hdfs locality.
The issue that namenode log router context is dicussed on this jara, another
issue about hdfs locality is discussed on HDFS-13248.
I‘m thinking about ways which are different from HDFS-13248 posted patch to
resovle hdfs locality, maybe we can resolve that issue by modifying RBF code
other than namenode.
> RBF: The RouterRPCServer should transfer CallerContext and client ip to
> NamenodeRpcServer
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-13293
> URL: https://issues.apache.org/jira/browse/HDFS-13293
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: maobaolong
> Assignee: Fei Hui
> Priority: Major
> Attachments: HDFS-13293.001.patch
>
>
> Otherwise, the namenode don't know the client's callerContext
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
