[
https://issues.apache.org/jira/browse/HDFS-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193397#comment-17193397
]
Fei Hui commented on HDFS-13293:
--------------------------------
[~aajisaka][~elgoiri] I think maybe we need to do three things.
* File a new jira and extend CallerContext in hadoop common, it can contains
many key value pairs.
* add real client ip to the caller context in this jira.
*hadoop.caller.context.enabled* has been used by audit log ,should we add new
parameter?
* File a new jira and Fix the way Yarn use CallerContext (Add key value to the
context)
What do you think ?
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
