[ 
https://issues.apache.org/jira/browse/HDFS-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899101#comment-16899101
 ] 

Hudson commented on HDFS-14685:
-------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17029 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17029/])
HDFS-14685. DefaultAuditLogger doesn't print CallerContext. Contributed 
(weichiu: rev b964b81f8509ba6cd938bc36f3acb5e3112b7ca2)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/HdfsAuditLogger.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSNamesystem.java


> DefaultAuditLogger doesn't print CallerContext
> ----------------------------------------------
>
>                 Key: HDFS-14685
>                 URL: https://issues.apache.org/jira/browse/HDFS-14685
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>            Reporter: xuzq
>            Assignee: xuzq
>            Priority: Major
>             Fix For: 3.3.0, 3.2.1, 3.1.3
>
>         Attachments: HDFS-14685-trunk-002.patch, HDFS-14685-trunk-003.patch
>
>
> If we not set dfs.namenode.audit.loggers(default is null), DefaultAuditLogger 
> will not print CallerConext into audit.log even if we set 
> hadoop.caller.context.enabled to true.
>  
> This bug also exists in 
> [HDFS-14625|https://issues.apache.org/jira/browse/HDFS-14625]
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to