Typo fix; referencing existing topic for plug-in restart
Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/245c21c6 Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/245c21c6 Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/245c21c6 Branch: refs/heads/master Commit: 245c21c693eac2bbeb4368f15b7e128c52520cc1 Parents: 8350307 Author: David Yozie <[email protected]> Authored: Mon Apr 3 14:05:20 2017 -0700 Committer: David Yozie <[email protected]> Committed: Mon Apr 3 14:05:20 2017 -0700 ---------------------------------------------------------------------- markdown/ranger/ranger-auditing.html.md.erb | 15 +++------------ 1 file changed, 3 insertions(+), 12 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/245c21c6/markdown/ranger/ranger-auditing.html.md.erb ---------------------------------------------------------------------- diff --git a/markdown/ranger/ranger-auditing.html.md.erb b/markdown/ranger/ranger-auditing.html.md.erb index 7f6fed0..18f2138 100644 --- a/markdown/ranger/ranger-auditing.html.md.erb +++ b/markdown/ranger/ranger-auditing.html.md.erb @@ -23,9 +23,9 @@ under the License. The HAWQ Ranger Plug-in Service supports storing auditing records in any of the Ranger auditing framework audit destinations, referred to as *audit sink*s. The `/usr/local/hawq/ranger/etc/ranger-hawq-audit.xml` file specifies the audit configuration. It contains sample definitions for the HDFS, Solr, and Log4j audit sinks. -As a best practice, configure one or more audit sinks in `ranger-hawq-audit.xml` before you register the HAWQ Ranger Plug-in Service. By default only the Log4j sink is enabled. Production deployments should use both a Solr and an HDFS audit sink, with the Solr destination configured to automatically purge audit records after some period of time. This configuration enables you to search the most recent audit records, while a keeping a full history of auditing records in HDFS. +As a best practice, configure one or more audit sinks in `ranger-hawq-audit.xml` before you register the HAWQ Ranger Plug-in Service. By default only the Log4j sink is enabled. Production deployments should use both a Solr and an HDFS audit sink, with the Solr destination configured to automatically purge audit records after some period of time. This configuration enables you to search the most recent audit records, while keeping a full history of auditing records in HDFS. -If you modify `ranger-hawq-audit.xml` after you have registered the HAWQ Ranger Plug-in, you must restart the plug-in for the changes to take effect. +If you modify `ranger-hawq-audit.xml` after you have registered the HAWQ Ranger Plug-in, you must restart the plug-in for the changes to take effect. See [Custom Configuration](ranger-integration-config.html#customconfig) for instructions. Full documentation for the Ranger auditing configuration properties and the Ranger auditing framework is available at [Ranger 0.5 Audit Configuration](https://cwiki.apache.org/confluence/display/RANGER/Ranger+0.5+Audit+Configuration). @@ -80,6 +80,7 @@ For example: <value>/usr/local/hawq_2_2_0_0/ranger/plugin-service/logs/spool/audit/solr</value> </property> ``` + ## <a id="hdfs"></a>Configuring HDFS Auditing To configure an HDFS audit sink, define these auditing properties in `ranger-hawq-audit.xml`: @@ -144,13 +145,3 @@ For example: <value>ranger_audit_logger</value> </property> ``` - -## <a id="reconfigure"></a>Changing the Plug-in Auditing Settings -If you modify `ranger-hawq-audit.xml` after you have registered the HAWQ Ranger Plug-in, you must either restart the HAWQ cluster or restart the plug-in for the changes to take effect. - -To restart only the HAWQ Ranger Plug-in: - -``` bash -$ /usr/local/hawq_2_2_0_0/ranger/bin/rps.sh stop -$ /usr/local/hawq_2_2_0_0/ranger/bin/rps.sh start -``` \ No newline at end of file
