Bug 702482 - Release note on setting max_connections configuration for cumin postgresql database
Summary: Release note on setting max_connections configuration for cumin postgresql da...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Release_Notes
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 2.0
: ---
Assignee: Alison Young
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 19:33 UTC by Trevor McKay
Modified: 2011-06-24 03:06 UTC (History)
1 user (show)

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.
Clone Of:
Environment:
Last Closed: 2011-06-24 03:06:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Release note content (10.71 KB, application/vnd.oasis.opendocument.text)
2011-05-06 20:19 UTC, Trevor McKay
no flags Details

Comment 1 Trevor McKay 2011-05-06 20:19:46 UTC
Created attachment 497451 [details]
Release note content

Comment 2 Trevor McKay 2011-05-24 19:24:43 UTC
Oops, just saw that there were never any flags set on this.

Comment 3 Misha H. Ali 2011-06-08 04:52:55 UTC
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.

Comment 4 Misha H. Ali 2011-06-08 04:52:55 UTC
    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.

Comment 5 Misha H. Ali 2011-06-08 04:55:22 UTC
    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:

Comment 10 Trevor McKay 2011-06-15 13:50:43 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.