Repository: incubator-impala
Updated Branches:
  refs/heads/master 924066a4f -> bc1feb34d


IMPALA-4431: [DOCS] Document max_audit_event_log_files startup option

Change-Id: I6777624e2139fdc062efaa778063e89e7d6d5772
Reviewed-on: http://gerrit.cloudera.org:8080/7369
Reviewed-by: Tim Armstrong <[email protected]>
Tested-by: Impala Public Jenkins


Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/da893308
Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/da893308
Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/da893308

Branch: refs/heads/master
Commit: da89330823f7559a57a68338fdf34c055c84d2fc
Parents: 924066a
Author: John Russell <[email protected]>
Authored: Thu Jul 6 16:46:29 2017 -0700
Committer: Impala Public Jenkins <[email protected]>
Committed: Fri Jul 7 05:48:21 2017 +0000

----------------------------------------------------------------------
 docs/topics/impala_auditing.xml | 16 +++++++++++++---
 docs/topics/impala_logging.xml  | 12 ++++++++++--
 2 files changed, 23 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/da893308/docs/topics/impala_auditing.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_auditing.xml b/docs/topics/impala_auditing.xml
index ae64c5e..10d9268 100644
--- a/docs/topics/impala_auditing.xml
+++ b/docs/topics/impala_auditing.xml
@@ -52,13 +52,23 @@ under the License.
       </li>
 
       <li>
-        Decide how many queries will be represented in each log file. By 
default,
-        Impala starts a new log file every 5000 queries. To specify a 
different number,
+        Decide how many queries will be represented in each audit event log 
file. By default,
+        Impala starts a new audit event log file every 5000 queries. To 
specify a different number,
         <ph audience="standalone">include
-        the option 
<codeph>-max_audit_event_log_file_size=<varname>number_of_queries</varname></codeph>
+        the option 
<codeph>--max_audit_event_log_file_size=<varname>number_of_queries</varname></codeph>
         in the <cmdname>impalad</cmdname> startup options</ph>.
       </li>
 
+      <li rev="2.9.0 IMPALA-4431">
+        In <keyword keyref="impala29_full"/> and higher, you can control how 
many
+        audit event log files are kept on each host. Specify the option
+        
<codeph>--max_audit_event_log_files=<varname>number_of_log_files</varname></codeph>
+        in the <cmdname>impalad</cmdname> startup options. Once the limit is 
reached, older
+        files are rotated out using the same mechanism as for other Impala log 
files.
+        The default value for this setting is 0, representing an unlimited 
number of audit
+        event log files.
+      </li>
+
       <li> 
         Use a cluster manager with governance capabilities to filter, 
visualize,
         and produce reports based on the audit logs collected

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/da893308/docs/topics/impala_logging.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml
index 5238e8b..1d7e762 100644
--- a/docs/topics/impala_logging.xml
+++ b/docs/topics/impala_logging.xml
@@ -70,6 +70,14 @@ under the License.
         enabled. See <xref href="impala_auditing.xml#auditing"/> for details.
       </p>
 
+      <p rev="2.9.0 IMPALA-4431">
+        In <keyword keyref="impala29_full"/> and higher, you can control how 
many
+        audit event log files are kept on each host through the
+        <codeph>--max_audit_event_log_files</codeph> startup option for the
+        <cmdname>impalad</cmdname> daemon, similar to the 
<codeph>--max_log_files</codeph>
+        option for regular log files.
+      </p>
+
       <p rev="2.2.0">
         The lineage feature introduced in Impala 2.2.0 produces a separate 
lineage log file when
         enabled. See <xref href="impala_lineage.xml#lineage"/> for details.
@@ -159,7 +167,7 @@ under the License.
         </li>
 
         <li>
-          The <codeph>-logbuflevel</codeph> startup flag for the 
<cmdname>impalad</cmdname> daemon specifies how
+          The <codeph>--logbuflevel</codeph> startup flag for the 
<cmdname>impalad</cmdname> daemon specifies how
           often the log information is written to disk. The default is 0, 
meaning that the log is immediately
           flushed to disk when Impala outputs an important messages such as a 
warning or an error, but less
           important messages such as informational ones are buffered in memory 
rather than being flushed to disk
@@ -215,7 +223,7 @@ under the License.
       </p>
 
       <p>
-        In Impala 2.2 and higher, the <codeph>-max_log_files</codeph> 
configuration option specifies how many log
+        In Impala 2.2 and higher, the <codeph>--max_log_files</codeph> 
configuration option specifies how many log
         files to keep at each severity level. You can specify an appropriate 
setting for each Impala-related daemon
         (<cmdname>impalad</cmdname>, <cmdname>statestored</cmdname>, and 
<cmdname>catalogd</cmdname>). The default
         value is 10, meaning that Impala preserves the latest 10 log files for 
each severity level

Reply via email to