You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by janebeckman <gi...@git.apache.org> on 2016/10/24 21:58:06 UTC
[GitHub] incubator-hawq-docs pull request #36: Note consistent use of Ambari vs. hawq...
GitHub user janebeckman opened a pull request:
https://github.com/apache/incubator-hawq-docs/pull/36
Note consistent use of Ambari vs. hawq config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/janebeckman/incubator-hawq-docs feature/cli_ambari_note
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq-docs/pull/36.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #36
----
----
---
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.
---
[GitHub] incubator-hawq-docs pull request #36: Note consistent use of Ambari vs. hawq...
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/36#discussion_r85015279
--- Diff: reference/cli/admin_utilities/hawqactivate.html.md.erb ---
@@ -4,6 +4,8 @@ title: hawq activate
Activates a standby master host and makes it the active master for the HAWQ system.
+**Note:** If HAWQ was installed using Ambari, do not use `hawq activate` to activate a standby master host. The system catalogs could become unsynchronized if you mix Ambari and command line functions. For Ambari-managed HAWQ clusters, always use the Ambari administration interface to activate a standby master.
--- End diff --
Let's include a link to the ambari section here.
---
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.
---
[GitHub] incubator-hawq-docs pull request #36: Note consistent use of Ambari vs. hawq...
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/36#discussion_r85776994
--- Diff: bestpractices/general_bestpractices.html.md.erb ---
@@ -9,6 +9,8 @@ When using HAWQ, adhere to the following guidelines for best results:
- **Use a consistent `hawq-site.xml` file to configure your entire cluster**:
Configuration guc/parameters are located in `$GPHOME/etc/hawq-site.xml`. This configuration file resides on all HAWQ instances and can be modified by using the `hawq config` utility. You can use the same configuration file cluster-wide across both master and segments.
+
+ If you install and manage HAWQ using Ambari, do not use `hawq config` to set or change HAWQ configuration properties. Use the Ambari interface for all configuration changes. Configuration changes to `hawq-site.xml` made outside the Ambari interface will be overwritten when HAWQ restarted or reconfigured using Ambari.
--- End diff --
Missing word: when HAWQ **is** restarted
And/or edit for passive voice
---
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.
---
[GitHub] incubator-hawq-docs pull request #36: Note consistent use of Ambari vs. hawq...
Posted by dyozie <gi...@git.apache.org>.
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/36#discussion_r85016338
--- Diff: bestpractices/general_bestpractices.html.md.erb ---
@@ -9,6 +9,8 @@ When using HAWQ, adhere to the following guidelines for best results:
- **Use a consistent `hawq-site.xml` file to configure your entire cluster**:
Configuration guc/parameters are located in `$GPHOME/etc/hawq-site.xml`. This configuration file resides on all HAWQ instances and can be modified by using the `hawq config` utility. You can use the same configuration file cluster-wide across both master and segments.
+
+ If you install and manage HAWQ using Ambari, be aware that any property changes to `hawq-site.xml` made using the command line could be overwritten by Ambari. For Ambari-managed HAWQ clusters, always use the Ambari administration interface, not `hawq config`, to set or change HAWQ configuration properties.
--- End diff --
Because we know that Ambari will overwrite local changes, I don't think we should say this "could" happen. Maybe edit this note (globally) to be more succinct:
If you install and manage HAWQ using Ambari, do not use `hawq config` to set or change HAWQ configuration properties. Instead, use the Ambari interface for all configuration changes. Any property changes that are made to `hawq-site.xml` outside of the Ambari interface will be overwritten when when you restart or reconfigure HAWQ with 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.
---
[GitHub] incubator-hawq-docs pull request #36: Note consistent use of Ambari vs. hawq...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-hawq-docs/pull/36
---
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.
---