From 384b9cb2b5c1ce8771c53ea5bbd8a98bfb039c41 Mon Sep 17 00:00:00 2001 From: Jane Beckman Date: Mon, 24 Oct 2016 13:47:41 -0700 Subject: [PATCH 1/4] Not consistent use of Ambari vs. hawq config --- bestpractices/general_bestpractices.html.md.erb | 2 ++ reference/HAWQSiteConfig.html.md.erb | 2 ++ reference/cli/admin_utilities/hawqactivate.html.md.erb | 2 ++ reference/guc/guc_category-list.html.md.erb | 3 ++- reference/guc/guc_config.html.md.erb | 2 +- 5 files changed, 9 insertions(+), 2 deletions(-) diff --git a/bestpractices/general_bestpractices.html.md.erb b/bestpractices/general_bestpractices.html.md.erb index 6c663c3..5c15806 100644 --- a/bestpractices/general_bestpractices.html.md.erb +++ b/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. **Note:** While `postgresql.conf` still exists in HAWQ, any parameters defined in `hawq-site.xml` will overwrite configurations in `postgresql.conf`. For this reason, we recommend that you only use `hawq-site.xml` to configure your HAWQ cluster. diff --git a/reference/HAWQSiteConfig.html.md.erb b/reference/HAWQSiteConfig.html.md.erb index 7910606..c354f34 100644 --- a/reference/HAWQSiteConfig.html.md.erb +++ b/reference/HAWQSiteConfig.html.md.erb @@ -8,6 +8,8 @@ Configuration guc/parameters are located in `$GPHOME/etc/hawq-site.xml`. This co **Note:** While `postgresql.conf` still exists in HAWQ, any parameters defined in `hawq-site.xml` will overwrite configurations in `postgresql.conf`. For this reason, we recommend that you only use `hawq-site.xml` to configure your HAWQ cluster. +**Note:** 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 to set or change HAWQ configuration properties. + - **[About Server Configuration Parameters](../reference/guc/guc_config.html)** - **[Configuration Parameter Categories](../reference/guc/guc_category-list.html)** diff --git a/reference/cli/admin_utilities/hawqactivate.html.md.erb b/reference/cli/admin_utilities/hawqactivate.html.md.erb index e05b09a..2b37a64 100644 --- a/reference/cli/admin_utilities/hawqactivate.html.md.erb +++ b/reference/cli/admin_utilities/hawqactivate.html.md.erb @@ -4,6 +4,8 @@ title: hawq activate Activates a standby master host and makes it the active master for the HAWQ system. +**Note:** If HAWQ was installed using Ambari, do not use `hawq activate` to activate a standby master host. The system catalogs could become unsynchronized if you mix Ambari and command line functions. For Ambari-managed HAWQ clusters, always use the Ambari administration interface to activate a standby master. + ## Synopsis ``` pre diff --git a/reference/guc/guc_category-list.html.md.erb b/reference/guc/guc_category-list.html.md.erb index e77f925..56f6e73 100644 --- a/reference/guc/guc_category-list.html.md.erb +++ b/reference/guc/guc_category-list.html.md.erb @@ -4,7 +4,6 @@ title: Configuration Parameter Categories Configuration parameters affect categories of server behaviors, such as resource consumption, query tuning, and authentication. The following sections describe HAWQ configuration parameter categories. - ## Append-Only Table Parameters The following parameters configure the append-only tables feature of HAWQ. @@ -349,6 +348,8 @@ When automatic statistics collection is enabled, you can run `ANALYZE` automatic - [gp\_autostats\_mode](parameter_definitions.html#gp_autostats_mode) - [log\_autostats](parameter_definitions.html#log_autostats) +**Note:** If you install and manage HAWQ using Ambari, be aware that property changes made using `hawq config` could be overwritten by Ambari. For Ambari-managed HAWQ clusters, always use the Ambari administration interface to set or change HAWQ configuration properties. + ### Runtime Statistics Collection Parameters These parameters control the server statistics collection feature. When statistics collection is enabled, you can access the statistics data using the *pg\_stat* and *pg\_statio* family of system catalog views. diff --git a/reference/guc/guc_config.html.md.erb b/reference/guc/guc_config.html.md.erb index 50b8eb7..56a2456 100644 --- a/reference/guc/guc_config.html.md.erb +++ b/reference/guc/guc_config.html.md.erb @@ -27,7 +27,7 @@ Many of the configuration parameters have limitations on who can change them and By design, all HAWQ instances (including master and segments) host identical `hawq-site.xml` files. Using a common `hawq-site.xml` file across all HAWQ instances simplifies configuration of the cluster. Within each `hawq-site.xml` configuration file, some parameters are considered *segment* parameters, meaning that each segment instance looks to its own `hawq-site.xml` file to get the value of that parameter. By convention, these parameter names begin with the string `hawq_segment`. Others parameters are considered *master* parameters. By convention, these parameter names begin with the string `hawq_master`. Master parameters are only applied at the master instance and ignored by segments. -**Note:** If you use the `hawq config` utility to set configuration parameter values in `hawq-site.xml`, the utility synchronizes all configuration files. Any manual modifications that you made to individual `hawq-site.xml` files may be lost. +**Note:** If you use the `hawq config` utility to set configuration parameter values in `hawq-site.xml`, the utility synchronizes all configuration files. Any manual modifications that you made to individual `hawq-site.xml` files may be lost. Additionally, if you install and manage HAWQ using Ambari, do not use `hawq config` to configure HAWQ properties. If the cluster is restarted, Ambari will overwrite any changes made by `hawq config` For Ambari-managed HAWQ clusters, only use the Ambari administration interface to set or change HAWQ configuration properties. This table describes the values in the Set Classifications column of the table in the description of a server configuration parameter. From 1bb14ff00a7093f1bad61c93bee3a210a02f32c2 Mon Sep 17 00:00:00 2001 From: Jane Beckman Date: Fri, 28 Oct 2016 14:37:22 -0700 Subject: [PATCH 2/4] Edits --- bestpractices/general_bestpractices.html.md.erb | 2 +- reference/cli/admin_utilities/hawqactivate.html.md.erb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bestpractices/general_bestpractices.html.md.erb b/bestpractices/general_bestpractices.html.md.erb index 5c15806..1c49636 100644 --- a/bestpractices/general_bestpractices.html.md.erb +++ b/bestpractices/general_bestpractices.html.md.erb @@ -10,7 +10,7 @@ When using HAWQ, adhere to the following guidelines for best results: 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. + If you install and manage HAWQ using Ambari, do not use `hawq config` to set or change HAWQ configuration properties. Use the Ambari interface for all configuration changes. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when HAWQ restarted or reconfigured using Ambari. **Note:** While `postgresql.conf` still exists in HAWQ, any parameters defined in `hawq-site.xml` will overwrite configurations in `postgresql.conf`. For this reason, we recommend that you only use `hawq-site.xml` to configure your HAWQ cluster. diff --git a/reference/cli/admin_utilities/hawqactivate.html.md.erb b/reference/cli/admin_utilities/hawqactivate.html.md.erb index 2b37a64..7afd6c7 100644 --- a/reference/cli/admin_utilities/hawqactivate.html.md.erb +++ b/reference/cli/admin_utilities/hawqactivate.html.md.erb @@ -4,7 +4,7 @@ title: hawq activate Activates a standby master host and makes it the active master for the HAWQ system. -**Note:** If HAWQ was installed using Ambari, do not use `hawq activate` to activate a standby master host. The system catalogs could become unsynchronized if you mix Ambari and command line functions. For Ambari-managed HAWQ clusters, always use the Ambari administration interface to activate a standby master. +**Note:** If HAWQ was installed using Ambari, do not use `hawq activate` to activate a standby master host. The system catalogs could become unsynchronized if you mix Ambari and command line functions. For Ambari-managed HAWQ clusters, always use the Ambari administration interface to activate a standby master. For more information, see [Manging HAWQ Using Ambari](../../../admin/ambari-admin.html#topic1). ## Synopsis From 88616c3aa36f299d35bcd3d55f61e9c091bccadf Mon Sep 17 00:00:00 2001 From: Jane Beckman Date: Mon, 31 Oct 2016 13:59:30 -0700 Subject: [PATCH 3/4] Edit --- bestpractices/general_bestpractices.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bestpractices/general_bestpractices.html.md.erb b/bestpractices/general_bestpractices.html.md.erb index 1c49636..ed1bc65 100644 --- a/bestpractices/general_bestpractices.html.md.erb +++ b/bestpractices/general_bestpractices.html.md.erb @@ -10,7 +10,7 @@ When using HAWQ, adhere to the following guidelines for best results: 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, do not use `hawq config` to set or change HAWQ configuration properties. Use the Ambari interface for all configuration changes. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when HAWQ restarted or reconfigured using Ambari. + If you install and manage HAWQ using Ambari, do not use `hawq config` to set or change HAWQ configuration properties. Use the Ambari interface for all configuration changes. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when you restart or reconfigured HAWQ using Ambari. **Note:** While `postgresql.conf` still exists in HAWQ, any parameters defined in `hawq-site.xml` will overwrite configurations in `postgresql.conf`. For this reason, we recommend that you only use `hawq-site.xml` to configure your HAWQ cluster. From 617dad9da2c9dc1c6ef74889b2e399888bda9f65 Mon Sep 17 00:00:00 2001 From: Jane Beckman Date: Mon, 31 Oct 2016 14:18:59 -0700 Subject: [PATCH 4/4] fix typo --- bestpractices/general_bestpractices.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bestpractices/general_bestpractices.html.md.erb b/bestpractices/general_bestpractices.html.md.erb index ed1bc65..503887b 100644 --- a/bestpractices/general_bestpractices.html.md.erb +++ b/bestpractices/general_bestpractices.html.md.erb @@ -10,7 +10,7 @@ When using HAWQ, adhere to the following guidelines for best results: 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, do not use `hawq config` to set or change HAWQ configuration properties. Use the Ambari interface for all configuration changes. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when you restart or reconfigured HAWQ using Ambari. + If you install and manage HAWQ using Ambari, do not use `hawq config` to set or change HAWQ configuration properties. Use the Ambari interface for all configuration changes. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when you restart or reconfigure HAWQ using Ambari. **Note:** While `postgresql.conf` still exists in HAWQ, any parameters defined in `hawq-site.xml` will overwrite configurations in `postgresql.conf`. For this reason, we recommend that you only use `hawq-site.xml` to configure your HAWQ cluster.