[
https://issues.apache.org/jira/browse/HDFS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404437#comment-16404437
]
maobaolong commented on HDFS-13270:
-----------------------------------
[~ywskycn] [~linyiqun] Thank you for watch this issue. After those day
research, i think HDFS-13293 can resolve this issue and HDFS-13248.
We can transfer the client ip and callerContext to the NameNode, so that
namenode and choose the right node for the origin client and get the origin
callercontext and log into the namenode auditlog.
> RBF: Router audit logger
> ------------------------
>
> Key: HDFS-13270
> URL: https://issues.apache.org/jira/browse/HDFS-13270
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs
> Affects Versions: 3.2.0
> Reporter: maobaolong
> Priority: Major
>
> We can use router auditlogger to log the client info and cmd, because the
> FSNamesystem#Auditlogger's log think the client are all from router.
--
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
