[
https://issues.apache.org/jira/browse/HAWQ-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903679#comment-15903679
]
ASF GitHub Bot commented on HAWQ-1372:
--------------------------------------
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/97#discussion_r105214050
--- Diff: markdown/admin/ambari-admin.html.md.erb ---
@@ -206,44 +208,22 @@ First ensure that the new node(s) has been configured
per the instructions found
23. (Optional.) If you enabled temporary password-based authentication
while preparing/configuring your HAWQ host systems, turn off password-based
authentication as described in [Apache HAWQ System
Requirements](../requirements/system-requirements.html#topic_pwdlessssh).
-#### <a id="manual-config-steps"></a>Manually Updating the HAWQ
Configuration
-If you need to expand your HAWQ cluster without restarting the HAWQ
service, follow these steps to manually apply the new HAWQ configuration. (Use
these steps *instead* of following Step 7 in the above procedure.):
+#### <a id="manual-config-steps"></a>Cluster Expansion Workaround
--- End diff --
Maybe rename this to "Workaround for Dynamic Cluster Expansion"?
> doc ambari hawq config change procedure that does not require cluster restart
> -----------------------------------------------------------------------------
>
> Key: HAWQ-1372
> URL: https://issues.apache.org/jira/browse/HAWQ-1372
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Documentation
> Reporter: Lisa Owen
> Assignee: David Yozie
> Priority: Minor
>
> document the workaround for updating hawq configuration via ambari (for
> ambari-managed clusters) in cases where a complete cluster restart cannot be
> tolerated:
> update config via ambari, do not restart
> update config via "hawq config -c xxx -v xxx"
> hawq stop cluster --reload
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
