Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D3753200C32 for ; Thu, 9 Mar 2017 20:22:11 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D1F26160B75; Thu, 9 Mar 2017 19:22:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 27939160B5F for ; Thu, 9 Mar 2017 20:22:11 +0100 (CET) Received: (qmail 2842 invoked by uid 500); 9 Mar 2017 19:22:05 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 2823 invoked by uid 99); 9 Mar 2017 19:22:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2017 19:22:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8F7BF1A0203 for ; Thu, 9 Mar 2017 19:22:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.02 X-Spam-Level: X-Spam-Status: No, score=-4.02 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id RkxtYq3nYE7C for ; Thu, 9 Mar 2017 19:22:03 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 852C45F39F for ; Thu, 9 Mar 2017 19:22:02 +0000 (UTC) Received: (qmail 2513 invoked by uid 99); 9 Mar 2017 19:22:01 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2017 19:22:01 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 94191DFF56; Thu, 9 Mar 2017 19:22:01 +0000 (UTC) From: dyozie To: dev@hawq.incubator.apache.org Reply-To: dev@hawq.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-hawq-docs pull request #97: HAWQ-1372 - doc config change without ... Content-Type: text/plain Message-Id: <20170309192201.94191DFF56@git1-us-west.apache.org> Date: Thu, 9 Mar 2017 19:22:01 +0000 (UTC) archived-at: Thu, 09 Mar 2017 19:22:12 -0000 Github user dyozie commented on a diff in the pull request: https://github.com/apache/incubator-hawq-docs/pull/97#discussion_r105239316 --- Diff: markdown/admin/ambari-admin.html.md.erb --- @@ -368,6 +348,49 @@ All of the listed steps are mandatory. This ensures that HAWQ service remains fu 4. Restart HAWQ service to propagate the configuration change to all Ambari agents. This will synchronize the password on the host machines with the password that you specified in Ambari. + +## Updating HAWQ Configuration Without Cluster Restart +There may be circumstances, such as during dynamic cluster expansion, when you must update HAWQ configuration parameters but cannot tolerate cluster downtime in your Ambari-managed cluster. In these situations, perform the following workaround to update and reload HAWQ configuration changes without a complete cluster restart. + +**Note**: Use this procedure for setting or updating only those HAWQ server configuration parameters with a set classification of reload. + +1. Use the Ambari console UI to set and save the desired HAWQ configuration parameter(s) via the **HAWQ** service **Settings**, **Configs >Settings**, and/or **Configs >Advanced** tabs. Make sure to note the configuration parameter names and new values. You may need to hover the mouse over the configuration field to identify the HAWQ parameter name. + + **Note**: After updating the configuration parameters, do *not* restart the HAWQ service. + +1. Use HAWQ command line utilities to update the same HAWQ configuration parameters: + 1. Log in to the HAWQ master host as a HAWQ administrator and source greenplum_path.sh: + + ``` shell + $ ssh gpadmin@ + gpadmin@master$ source /usr/local/hawq/greenplum_path.sh + ``` + + 2. Identify the current value of the HAWQ configuration parameter: + + ``` shell + gpadmin@master$ hawq config -s + ``` + + 3. Set the configuration parameter to the new value: + + ``` shell + gpadmin@master$ hawq config -c -v + ``` + + Perform Steps 2 and 3 for each configuration parameter you set or updated via Ambari. + +3. Reload the HAWQ configuration; this operation does not restart the cluster: + + ``` shell + gpadmin@master$ hawq stop cluster --reload + ``` + +4. Verify that each parameter was updated: + + ```shell + gpadmin@master$ hawq config -s + ``` --- End diff -- Seems like this section also needs a closing sentence about when the changes refresh in 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 infrastructure@apache.org or file a JIRA ticket with INFRA. ---