[GitHub] incubator-hawq-docs pull request #108: add config section, misc

[lisakowen]

Github user lisakowen closed the pull request at:

https://github.com/apache/incubator-hawq-docs/pull/108


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq-docs pull request #108: add config section, misc

[lisakowen]

Github user lisakowen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/108#discussion_r109044924
  
--- Diff: markdown/ranger/ranger-integration-config.html.md.erb ---
@@ -124,8 +116,39 @@ Once the connection between HAWQ and Ranger is 
configured, you can either set up
 4. Click **Add Property...** and add the new property, 
`hawq_acl_type=ranger` property. (If the property already exists, change its 
value from `standalone` (the default) to `ranger`.)
 5. Click **Save** to save your changes.
 6. Select **Service Actions > Restart All** and confirm that you want to 
restart the HAWQ cluster.
-
 
-## Changing the Frequency of Policy Caching
+
+##  Custom Configuration
+
+Configuration files for the HAWQ Ranger Plug-in Service are located in the 
`$GPHOME/ranger/etc` directory. These files include:
+
+| File |  Description |
+|-|---|
+| ranger-hawq-audit.xml |  HAWQ Ranger audit-related configuration, 
including the audit provider (log4j, Solr, HDFS) and provider-specific 
configuration |
+| ranger-hawq-security.xml |  HAWQ Ranger service configuration, including 
the policy change polling interval |
+| rps.properties |  HAWQ Ranger deployment-related configuration, 
including the RPS port definition and JVM parameters|
+
+You should not need to modify RPS configuration in a default installation. 
 Any configuration changes you do make after you have registered the HAWQ 
Ranger Plug-in requires a restart of the service. You can either restart the 
HAWQ cluster or restart just the HAWQ Ranger Plug-in Service:
+
+``` shell
+gpadmin@master$ /usr/local/hawq/ranger/bin/rps.sh stop
+gpadmin@master$ /usr/local/hawq/ranger/bin/rps.sh start
+```
+
+### Changing the Frequency of Policy Caching
  
-You may wish to change the frequency of policy caching to suit your 
individual needs.
\ No newline at end of file
+The default polling interval for HAWQ RPS policy updates is 30 seconds. To 
increase or decrease this value, update the 
`ranger.plugin.hawq.policy.pollIntervalMs` property setting in the 
`ranger-hawq-security.xml` file:
--- End diff --

incorporated your updates, david.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq-docs pull request #108: add config section, misc

[lisakowen]

GitHub user lisakowen opened a pull request:

https://github.com/apache/incubator-hawq-docs/pull/108

add config section, misc

added a config section.  also made some minor wording edits.

noticed some control-m s in the diff.  not sure where those are coming from 
... don't seem to affect the html generation.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lisakowen/incubator-hawq-docs 
feature/ranger-addcfg

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq-docs/pull/108.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #108


commit 6881caadc01503a476810d70dabd86415a625a9f
Author: Lisa Owen 
Date:   2017-03-30T20:46:56Z

add config section, minor wording edits




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---