[
https://issues.apache.org/jira/browse/HDFS-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623392#comment-16623392
]
Fei Hui commented on HDFS-13293:
--------------------------------
Tests are following:
Add configuration to namenode
{code:java}
<property>
<name>hadoop.caller.context.enabled</name>
<value>true</value>
</property>
{code}
Hdfs audit logs
{quote}
2018-09-20 14:23:44,494 INFO FSNamesystem.audit: allowed=true ugi=hadoop
ip=/10.83.78.54 cmd=getfileinfo src=/user/hadoop dst=null
perm=null proto=rpc callerContext=RouterCallIp:10.83.78.53
2018-09-20 14:23:44,539 INFO FSNamesystem.audit: allowed=true ugi=hadoop
ip=/10.83.78.54 cmd=listStatus src=/user/hadoop dst=null
perm=null proto=rpc callerContext=RouterCallIp:10.83.78.53
{quote}
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
