<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Disable log4j logging for HDFS audit log in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220657#M182542</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/12921/wbekker.html" nodeid="12921"&gt;@Ward Bekker&lt;/A&gt;&lt;/P&gt;&lt;P&gt;In the Ambari UI --&amp;gt; HDFS --&amp;gt; Configs --&amp;gt; Advanced --&amp;gt; "hadoop-env template" you will see the "SHARED_HADOOP_NAMENODE_OPTS" variable that is setting the &lt;/P&gt;&lt;PRE&gt;-Dhdfs.audit.logger=INFO,DRFAAUDIT&lt;/PRE&gt;&lt;P&gt;
Above actually controls the audit logging. So you might want to delete that "hdfs.audit.logger" system property from the if-else block (same for HADOOP_DATANODE_OPTS  option as well)&lt;/P&gt;&lt;PRE&gt;{% if java_version &amp;lt; 8 %}
SHARED_HADOOP_NAMENODE_OPTS= ........

{% else %}
SHARED_HADOOP_NAMENODE_OPTS=

{% endif %}&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;After that when we restart the HDFS components then in the &lt;STRONG&gt;"ps -ef | grep NameNode"&lt;/STRONG&gt; we should not see the "-Dhdfs.audit.logger=INFO,DRFAAUDIT"&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;</description>
    <pubDate>Thu, 04 May 2017 20:01:04 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2017-05-04T20:01:04Z</dc:date>
    <item>
      <title>Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220656#M182541</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;How can I disable the logging for the HDFS Audit log? My current config:&lt;/P&gt;&lt;PRE&gt;hdfs.audit.logger=INFO,console
log4j.logger.org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit=${hdfs.audit.logger}
log4j.additivity.org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit=false
log4j.appender.DRFAAUDIT=org.apache.log4j.DailyRollingFileAppender
log4j.appender.DRFAAUDIT.File=${hadoop.log.dir}/hdfs-audit.log
log4j.appender.DRFAAUDIT.layout=org.apache.log4j.PatternLayout
log4j.appender.DRFAAUDIT.layout.ConversionPattern=%d{ISO8601} %p %c{2}: %m%n
log4j.appender.DRFAAUDIT.DatePattern=.yyyy-MM-dd

&lt;/PRE&gt;</description>
      <pubDate>Thu, 04 May 2017 19:45:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220656#M182541</guid>
      <dc:creator>wbekker</dc:creator>
      <dc:date>2017-05-04T19:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220657#M182542</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/12921/wbekker.html" nodeid="12921"&gt;@Ward Bekker&lt;/A&gt;&lt;/P&gt;&lt;P&gt;In the Ambari UI --&amp;gt; HDFS --&amp;gt; Configs --&amp;gt; Advanced --&amp;gt; "hadoop-env template" you will see the "SHARED_HADOOP_NAMENODE_OPTS" variable that is setting the &lt;/P&gt;&lt;PRE&gt;-Dhdfs.audit.logger=INFO,DRFAAUDIT&lt;/PRE&gt;&lt;P&gt;
Above actually controls the audit logging. So you might want to delete that "hdfs.audit.logger" system property from the if-else block (same for HADOOP_DATANODE_OPTS  option as well)&lt;/P&gt;&lt;PRE&gt;{% if java_version &amp;lt; 8 %}
SHARED_HADOOP_NAMENODE_OPTS= ........

{% else %}
SHARED_HADOOP_NAMENODE_OPTS=

{% endif %}&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;After that when we restart the HDFS components then in the &lt;STRONG&gt;"ps -ef | grep NameNode"&lt;/STRONG&gt; we should not see the "-Dhdfs.audit.logger=INFO,DRFAAUDIT"&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2017 20:01:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220657#M182542</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-05-04T20:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220658#M182543</link>
      <description>&lt;P&gt;excellent, thx!&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2017 20:06:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220658#M182543</guid>
      <dc:creator>wbekker</dc:creator>
      <dc:date>2017-05-04T20:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220659#M182544</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/12921/wbekker.html" nodeid="12921"&gt;@Ward Bekker&lt;/A&gt; we don't recommend disabling HDFS audit logging. It's hard to debug many HDFS issues without the audit log. Just curious, why would you like to disable it?&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 21:56:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220659#M182544</guid>
      <dc:creator>ArpitAgarwal</dc:creator>
      <dc:date>2017-05-08T21:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220660#M182545</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/126/aagarwal.html" nodeid="126"&gt;@Arpit Agarwal&lt;/A&gt; good point. The customer uses ranger audit logging. What extra information is in the hdfs audit log, what is not already in the ranger audit logs.&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 21:59:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220660#M182545</guid>
      <dc:creator>wbekker</dc:creator>
      <dc:date>2017-05-08T21:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220661#M182546</link>
      <description>&lt;P&gt;Sorry I missed the notification of your reply. That is also a good question. I have not yet come across a customer setup where HDFS audit logging is disabled and Ranger audit logs is on.&lt;/P&gt;&lt;P&gt;I'd recommend tagging someone from Ranger to make sure.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2017 03:39:50 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220661#M182546</guid>
      <dc:creator>ArpitAgarwal</dc:creator>
      <dc:date>2017-05-23T03:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: Disable log4j logging for HDFS audit log</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220662#M182547</link>
      <description>&lt;P&gt;In my experience, if you remove the indicated flags, you still get audit logging - but those logs never get purged.&lt;/P&gt;&lt;P&gt;Perhaps it would be better to leave the flags, but to change "INFO" to "OFF", rendering something like:&lt;/P&gt;&lt;PRE&gt;-Dhdfs.audit.logger=OFF,DRFAAUDIT"&lt;/PRE&gt;&lt;P&gt;?&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2018 23:01:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Disable-log4j-logging-for-HDFS-audit-log/m-p/220662#M182547</guid>
      <dc:creator>jarnold</dc:creator>
      <dc:date>2018-05-18T23:01:39Z</dc:date>
    </item>
  </channel>
</rss>

