hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dyozie <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #93: Feature/hawq 1307 best pract
Date Fri, 03 Feb 2017 17:12:21 GMT
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.
---

Mime
View raw message