Difference between revisions of "No Free Workers Error"

From Roaring Penguin
Jump to: navigation, search
m (Admin moved page No Free Slaves Error to No Free Workers Error: Slaves are now called workers)
Line 3: Line 3:
 
If you have not already, you should install PGBouncer as per Appendix G in the Administration Guide. This can greatly increase database performance.
 
If you have not already, you should install PGBouncer as per Appendix G in the Administration Guide. This can greatly increase database performance.
  
You can increase the maximum number of MimeDefang processes as follows.
+
You can increase the maximum number of MIMEDefang processes as follows.
  
 
First: Ensure that you have enough free memory using the 'free' command.  
 
First: Ensure that you have enough free memory using the 'free' command.  
  
Each MimeDefang process can take around 20-25MB of memory or more depending on how many lock slots are made available.
+
Each MIMEDefang process can take around 20-25MB of memory or more depending on how many lock slots are made available.
  
 
In the file /etc/postgresql/X.X/main/postgresql.conf (the X.X will be your PostgreSQL version number), there is a line for
 
In the file /etc/postgresql/X.X/main/postgresql.conf (the X.X will be your PostgreSQL version number), there is a line for
Line 13: Line 13:
 
   max_connections
 
   max_connections
  
the default of which is 100. This represents the total number or connections allowed to PostgreSQL, given by the sum of all MIMEDefang slaves from all cluster members PLUS the number of expected simultaneous human connections. Thus, once you increase the max_connections, you will also need to increase the per-member connection limit by no more than ((new limit)-(old limit))/(number of nodes) using:
+
the default of which is 100. This represents the total number or connections allowed to PostgreSQL, given by the sum of all MIMEDefang workers from all cluster members PLUS the number of expected simultaneous human connections. Thus, once you increase the max_connections, you will also need to increase the per-member connection limit by no more than ((new limit)-(old limit))/(number of nodes) using:
  
 
   mx_maximum=
 
   mx_maximum=

Revision as of 16:35, 9 February 2018

Under Construction

If you have not already, you should install PGBouncer as per Appendix G in the Administration Guide. This can greatly increase database performance.

You can increase the maximum number of MIMEDefang processes as follows.

First: Ensure that you have enough free memory using the 'free' command.

Each MIMEDefang process can take around 20-25MB of memory or more depending on how many lock slots are made available.

In the file /etc/postgresql/X.X/main/postgresql.conf (the X.X will be your PostgreSQL version number), there is a line for

  max_connections

the default of which is 100. This represents the total number or connections allowed to PostgreSQL, given by the sum of all MIMEDefang workers from all cluster members PLUS the number of expected simultaneous human connections. Thus, once you increase the max_connections, you will also need to increase the per-member connection limit by no more than ((new limit)-(old limit))/(number of nodes) using:

 mx_maximum=

in the [mimedefang] section) of the /etc/mail/canit/canit.conf file.