Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/36#discussion_r85016338
--- Diff: bestpractices/general_bestpractices.html.md.erb ---
@@ -9,6 +9,8 @@ When using HAWQ, adhere to the following guidelines for
best results:
- **Use a consistent `hawq-site.xml` file to configure your entire
cluster**:
Configuration guc/parameters are located in
`$GPHOME/etc/hawq-site.xml`. This configuration file resides on all HAWQ
instances and can be modified by using the `hawq config` utility. You can use
the same configuration file cluster-wide across both master and segments.
+
+ If you install and manage HAWQ using Ambari, be aware that any
property changes to `hawq-site.xml` made using the command line could be
overwritten by Ambari. For Ambari-managed HAWQ clusters, always use the Ambari
administration interface, not `hawq config`, to set or change HAWQ
configuration properties.
--- End diff --
Because we know that Ambari will overwrite local changes, I don't think we
should say this "could" happen. Maybe edit this note (globally) to be more
succinct:
If you install and manage HAWQ using Ambari, do not use `hawq config` to
set or change HAWQ configuration properties. Instead, use the Ambari interface
for all configuration changes. Any property changes that are made to
`hawq-site.xml` outside of the Ambari interface will be overwritten when when
you restart or reconfigure HAWQ with Ambari.
---
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.
---
