[
https://issues.apache.org/jira/browse/HAWQ-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893300#comment-15893300
]
Lisa Owen commented on HAWQ-1372:
---------------------------------
i agree it would be more user-friendly for the admin of an ambari-managed
cluster to not have to:
- restart the cluster for a config change
- update the same config in two places, manually or not, as the workaround
suggests
ambari knows it is managing hawq, but does hawq know when ambari is managing it?
in any case, you may want to open a new JIRA identifying component "command
line tools" with your request.
> 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)
