Github user radarwave commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/129#discussion_r135990959
--- 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.
-When you set `max_connections`, you must also set the dependent parameter
`max_prepared_transactions`. This value must be at least as large as the value
of `max_connections`, and all HAWQ instances should be set to the same value.
+When you set `max_connections`, you can also set the value for the maximum
concurrent connections for the segments by using `seg_max_connections`. Setting
this parameter overrides the value of `max_connections` on the segment
instances.
Example `$GPHOME/etc/hawq-site.xml` configuration:
``` xml
<property>
<name>max_connections</name>
- <value>500</value>
+ <value>200</value>
</property>
<property>
- <name>max_prepared_transactions</name>
+ <name>seg_max_connectionss</name>
--- End diff --
As I mentioned above, this should better to be 3000 as our default value.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
