| Summary: | Release note on setting max_connections configuration for cumin postgresql database | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Trevor McKay <tmckay> | ||||
| Component: | Release_Notes | Assignee: | Alison Young <alyoung> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | Development | CC: | mhusnain | ||||
| Target Milestone: | 2.0 | Keywords: | Documentation | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Depending on the configuration and number of cumin users, the default max_connection configuration value in the PostgreSQL database can be changed to accommodate a large number of users.
The max_connections parameter in /var/lib/pgsql/data/postgresql.conf specifies the maximum number of concurrent connections allowed by the PostgreSQL server. This value is set to 100 by default.
The maximum number of concurrent connections needed by cumin can be estimated with the following formula:
(cumin-web instances * 36) + (cumin-data instances) + 2
For a default cumin configuration this number will be 43 but with multiple cumin-web instances, the number increases significantly. Ensure that the value of the max_connections parameter is set at a value that can accommodate the number of connections required by cumin and other applications that connect to the PostgreSQL server.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-24 03:06:09 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Oops, just saw that there were never any flags set on this. Depending on the configuration and number of cumin users, the default max_connection configuration value in the postgreSQL database can be changed to accommodate a large number of users.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Depending on the configuration and number of <systemitem class="process">cumin</systemitem> users, the default <parameter>max_connection</parameter> configuration value in the PostgreSQL database can be changed to accommodate a large number of users.
</para>
</entry>
<entry>
<para>
The max_connections parameter in /var/lib/pgsql/data/postgresql.conf specifies the maximum number of concurrent connections allowed by the PostgreSQL server. This value is set to 100 by default.
The maximum number of concurrent connections needed by cumin can be estimated with the following formula:
(cumin-web instances * 36) + (cumin-data instances) + 2
For a default cumin configuration this number will be 43 but with multiple cumin-web instances, the number increases significantly. Ensure that the value of the max_connections parameter is set at a value that can accommodate the number of connections required by cumin and other applications that connect to the PostgreSQL server.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,8 +1,4 @@
-Depending on the configuration and number of <systemitem class="process">cumin</systemitem> users, the default <parameter>max_connection</parameter> configuration value in the PostgreSQL database can be changed to accommodate a large number of users.
- </para>
- </entry>
- <entry>
- <para>
+Depending on the configuration and number of cumin users, the default max_connection configuration value in the PostgreSQL database can be changed to accommodate a large number of users.
The max_connections parameter in /var/lib/pgsql/data/postgresql.conf specifies the maximum number of concurrent connections allowed by the PostgreSQL server. This value is set to 100 by default.
The maximum number of concurrent connections needed by cumin can be estimated with the following formula:
Removed private flag on BZ, restate description with inappropriate bits removed.
> Description of problem:
>
> Depending on the configuration at a particular site and the number of cumin
> users, it may be necessary to increase the default max_connections
> configuration value in the postgres database.
|
Created attachment 497451 [details] Release note content