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

Hudson commented on HDFS-10209:
-------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #9606 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/9606/])
Revert "HDFS-10209. Support enable caller context in HDFS namenode audit (xyao: 
rev 4895c73dd493a53eab43f0d16e92c19af15c460b)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeReconfigure.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
HDFS-10209. Support enable caller context in HDFS namenode audit log (xyao: rev 
5566177c9af913baf380811dbbb1fa7e70235491)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeReconfigure.java


> Support enable caller context in HDFS namenode audit log without restart 
> namenode
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-10209
>                 URL: https://issues.apache.org/jira/browse/HDFS-10209
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaobing Zhou
>             Fix For: 2.9.0
>
>         Attachments: HDFS-10209-HDFS-9000.000.patch, 
> HDFS-10209-HDFS-9000.001.patch
>
>
> RPC caller context is a useful feature to track down the origin of the 
> caller, which can track down "bad" jobs that overload the namenode. This 
> ticket is opened to allow enabling caller context without namenode restart.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to