[
https://issues.apache.org/jira/browse/HAWQ-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892229#comment-15892229
]
Jon Roberts commented on HAWQ-1372:
-----------------------------------
Would it be possible for the installer to save the credentials for Ambari so
that "hawq config" can also update Ambari's database? It certainly would be
more streamlined for Administrators than telling them to manually do it in
Ambari.
"hawq config" should raise INFO/WARN messages about updating Ambari too.
Example:
hawq config -c hawq_rm_stmt_vseg_memory -v 16gb
INFO: Updated Ambari with hawq_rm_stmt_vseg_memory=16gb
or
hawq config -c hawq_rm_stmt_vseg_memory -v 16gb
WARN: Failed to update Ambari with hawq_rm_stmt_vseg_memory=16gb. Please
update Ambari credentials.
"hawq" should also get a new command to store the credentials for Ambari.
Example:
hawq ambari -u admin -w admin -h myhost -p 8080
> 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)
