hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dyozie <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #60: HAWQ-1151 - add ambari procedures
Date Tue, 15 Nov 2016 00:17:35 GMT
Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/60#discussion_r87920277
  
    --- Diff: clientaccess/client_auth.html.md.erb ---
    @@ -101,51 +101,45 @@ For example, in `$GPHOME/etc/hawq-site.xml`:
       </property>
     ```
     
    -The following steps set the parameter values with the HAWQ utility `hawq config`.
    -
    -### <a id="ip142411"></a>To change the number of allowed connections 
    +**Note:** Raising the values of these parameters may cause HAWQ to request more shared
memory. To mitigate this effect, consider decreasing other memory-related server configuration
parameters such as [gp\_cached\_segworkers\_threshold](../reference/guc/parameter_definitions.html#gp_cached_segworkers_threshold).
     
    -1.  Log into the HAWQ master host as the HAWQ administrator and source the file `/usr/local/hawq/greenplum_path.sh`.
    -2.  Set the value of the `max_connections` parameter. This `hawq config` command sets
the value to 100 on all HAWQ instances.
     
    -    ``` bash
    -    $ hawq config -c max_connections -v 100
    -    ```
    +### <a id="ip142411"></a>Setting the number of allowed connections
     
    -    This configuration command sets the value for the master.
    +You will perform different procedures to set connection-related server configuration
parameters for your HAWQ cluster depending upon whether you manage your cluster from the command
line or use Ambari. If you use Ambari to manage your HAWQ cluster, you must ensure that you
update server configuration parameters via the Ambari Web UI only. If you manage your HAWQ
cluster from the command line, you will use the `hawq config` command line utility to set
server configuration parameters.
     
    -3.  Set the value of the `seg_max_connections` parameter. This `hawq config` command
sets the value to 6400 on all HAWQ instances.
    +If you use Ambari to manage your cluster:
     
    -    ``` bash
    -    $ hawq config -c seg_max_connections -v 6400
    -    ```
    +1. Set the `max_connections`, `seg_max_connections`, and `max_prepared_transactions`
configuration properties via the HAWQ service **Configs > Advanced > Custom hawq-site**
drop down, providing values appropriate for your HAWQ deployment.
    --- End diff --
    
    I think I'd remove ", providing values appropriate for your HAWQ deployment" 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.
---

Mime
View raw message