You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by janebeckman <gi...@git.apache.org> on 2017/02/03 00:05:32 UTC
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
GitHub user janebeckman opened a pull request:
https://github.com/apache/incubator-hawq-docs/pull/93
Feature/hawq 1307 best pract
Created a new section "Best Practices for Configuring HAWQ Parameters" and removed parameter material from the "Operating" section. Updated "Operating" to create an umbrella heading for the monitoring tasks, and clarified that Ambari clusters should use Ambari for performing equivalent tasks.
https://issues.apache.org/jira/browse/HAWQ-1307
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/janebeckman/incubator-hawq-docs feature/HAWQ-1307_BestPract
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq-docs/pull/93.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 #93
----
commit 76c3c3c55bd67f1bb030493790b6a2e2c374ff58
Author: Jane Beckman <jb...@pivotal.io>
Date: 2017-02-02T22:16:48Z
Rework Best Practices
commit 847b3efa5c1c11fb6a2b00a17cbda6d9391fb904
Author: Jane Beckman <jb...@pivotal.io>
Date: 2017-02-02T23:24:41Z
Navigation for Best Practices
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Posted by janebeckman <gi...@git.apache.org>.
Github user janebeckman commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/93#discussion_r99393681
--- Diff: markdown/bestpractices/operating_hawq_bestpractices.html.md.erb ---
@@ -23,21 +23,14 @@ under the License.
This topic provides best practices for operating HAWQ, including recommendations for stopping, starting and monitoring HAWQ.
-## <a id="best_practice_config"></a>Best Practices for Configuring HAWQ Parameters
+## <a id="task_qgk_bz3_1v"></a>Best Practices Using the Command Line to Start/Stop HAWQ Cluster Members
--- End diff --
That's weird. The space wasn't even visible in the file, and I had to delete words on either side and re-enter because it didn't think the space existed. I've seen these phantom spaces before, but this is the first one I had trouble deleting.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Posted by janebeckman <gi...@git.apache.org>.
Github user janebeckman closed the pull request at:
https://github.com/apache/incubator-hawq-docs/pull/93
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/93#discussion_r99379948
--- Diff: markdown/bestpractices/operating_hawq_bestpractices.html.md.erb ---
@@ -23,21 +23,14 @@ under the License.
This topic provides best practices for operating HAWQ, including recommendations for stopping, starting and monitoring HAWQ.
-## <a id="best_practice_config"></a>Best Practices for Configuring HAWQ Parameters
+## <a id="task_qgk_bz3_1v"></a>Best Practices Using the Command Line to Start/Stop HAWQ Cluster Members
-The HAWQ configuration guc/parameters are located in `$GPHOME/etc/hawq-site.xml`. This configuration file resides on all HAWQ instances and can be modified either by the Ambari interface or the command line.
+The following best practices are recommended for best results when using `hawq start` and `hawq stop` to manage your HAWQ cluster.
-If you install and manage HAWQ using Ambari, use the Ambari interface for all configuration changes. Do not use command line utilities such as `hawq config` to set or change HAWQ configuration properties for Ambari-managed clusters. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when you restart or reconfigure HAWQ using Ambari.
-
-If you manage your cluster using command line tools instead of Ambari, use a consistent `hawq-site.xml` file to configure your entire cluster.
-
-**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. For Ambari clusters, always use Ambari for configuring `hawq-site.xml` parameters.
-
-## <a id="task_qgk_bz3_1v"></a>Best Practices to Start/Stop HAWQ Cluster Members
-
-For best results in using `hawq start` and `hawq stop` to manage your HAWQ system, the following best practices are recommended.
-
-- Issue the `CHECKPOINT` command to update and flush all data files to disk and update the log file before stopping the cluster. A checkpoint ensures that, in the event of a crash, files can be restored from the checkpoint snapshot.
+- Always use HAWQ management commands to start and stop HAWQ, rather than Postgres equivalents.
--- End diff --
Let's change "rather than" to "instead of" in this case.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/93#discussion_r99379440
--- Diff: markdown/bestpractices/operating_hawq_bestpractices.html.md.erb ---
@@ -23,21 +23,14 @@ under the License.
This topic provides best practices for operating HAWQ, including recommendations for stopping, starting and monitoring HAWQ.
-## <a id="best_practice_config"></a>Best Practices for Configuring HAWQ Parameters
+## <a id="task_qgk_bz3_1v"></a>Best Practices Using the Command Line to Start/Stop HAWQ Cluster Members
-The HAWQ configuration guc/parameters are located in `$GPHOME/etc/hawq-site.xml`. This configuration file resides on all HAWQ instances and can be modified either by the Ambari interface or the command line.
+The following best practices are recommended for best results when using `hawq start` and `hawq stop` to manage your HAWQ cluster.
--- End diff --
I think we should remove "for best results" as it seems redundant.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/93#discussion_r99379315
--- Diff: markdown/bestpractices/operating_hawq_bestpractices.html.md.erb ---
@@ -23,21 +23,14 @@ under the License.
This topic provides best practices for operating HAWQ, including recommendations for stopping, starting and monitoring HAWQ.
-## <a id="best_practice_config"></a>Best Practices for Configuring HAWQ Parameters
+## <a id="task_qgk_bz3_1v"></a>Best Practices Using the Command Line to Start/Stop HAWQ Cluster Members
--- End diff --
Let's get rid of the extra spacing here.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/93#discussion_r99380056
--- Diff: markdown/bestpractices/operating_hawq_bestpractices.html.md.erb ---
@@ -23,21 +23,14 @@ under the License.
This topic provides best practices for operating HAWQ, including recommendations for stopping, starting and monitoring HAWQ.
-## <a id="best_practice_config"></a>Best Practices for Configuring HAWQ Parameters
+## <a id="task_qgk_bz3_1v"></a>Best Practices Using the Command Line to Start/Stop HAWQ Cluster Members
-The HAWQ configuration guc/parameters are located in `$GPHOME/etc/hawq-site.xml`. This configuration file resides on all HAWQ instances and can be modified either by the Ambari interface or the command line.
+The following best practices are recommended for best results when using `hawq start` and `hawq stop` to manage your HAWQ cluster.
-If you install and manage HAWQ using Ambari, use the Ambari interface for all configuration changes. Do not use command line utilities such as `hawq config` to set or change HAWQ configuration properties for Ambari-managed clusters. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when you restart or reconfigure HAWQ using Ambari.
-
-If you manage your cluster using command line tools instead of Ambari, use a consistent `hawq-site.xml` file to configure your entire cluster.
-
-**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. For Ambari clusters, always use Ambari for configuring `hawq-site.xml` parameters.
-
-## <a id="task_qgk_bz3_1v"></a>Best Practices to Start/Stop HAWQ Cluster Members
-
-For best results in using `hawq start` and `hawq stop` to manage your HAWQ system, the following best practices are recommended.
-
-- Issue the `CHECKPOINT` command to update and flush all data files to disk and update the log file before stopping the cluster. A checkpoint ensures that, in the event of a crash, files can be restored from the checkpoint snapshot.
+- Always use HAWQ management commands to start and stop HAWQ, rather than Postgres equivalents.
+- Use `hawq start cluster` or `hawq restart cluster` to start the entire cluster, rather than starting the master and individual segments.
+- If you do decide to use `hawq start standby|master|segment` to start nodes individually, make sure you always start the standby before the active master. Otherwise, the standby can become unsynchronized with the active master.
--- End diff --
Remove "make sure you" in this sentence.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---