hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From radarwave <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #129: Update for current implementation of ...
Date Wed, 30 Aug 2017 07:39:29 GMT
Github user radarwave commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/129#discussion_r135990205
  
    --- Diff: markdown/clientaccess/client_auth.html.md.erb ---
    @@ -99,27 +99,25 @@ This example shows how to edit the `pg_hba.conf` file of the master
to allow rem
     
     HAWQ allocates some resources on a per-connection basis, so setting the maximum number
of connections allowed is recommended.
     
    -To limit the number of active concurrent sessions to your HAWQ system, you can configure
the `max_connections` server configuration parameter on master or the `seg_max_connections`
server configuration parameter on segments. These parameters are *local* parameters, meaning
that you must set them in the `hawq-site.xml` file of all HAWQ instances.
    +To limit the number of active concurrent sessions to your HAWQ system, you can configure
the `max_connections` server configuration parameter. This parameter is a *local* parameter,
meaning that you must set them in the `hawq-site.xml` file of all HAWQ instances.
    --- End diff --
    
    The previous one seems better:
    To limit the number of active concurrent sessions to your HAWQ system, you can configure
the `max_connections` server configuration parameter on master or the `seg_max_connections`
server configuration parameter on segments.
    
    Except that I think we don't need to mention it's a *local* parameter. We don't need to
set it in 'hawq-site.xml' unless we want one specify node to be different than others.



---
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