server/apache/mirrormanager.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 4c983b801b5b64487d04baa4d533fac6220f32c1
Author: Matt Domsch <Matt_Domsch(a)dell.com>
Date: Sat Apr 24 22:02:38 2010 -0500
mirrormanager.wsgi run 4 instances per app server (up from 2)
Reports from mirror admins that report_mirror is issuing "connection
refused" messages. This may be because we have added mirrors, but
have relatively few processes available to accept report_mirror
requests.
This change doubles the number of waiting web UI / XMLRPC processes
running on each app server, which will increase the number of
connections to the database also. A similar change was made recently
to increase the number of mirrorlist WSGI apps running to solve a
similar problem.
diff --git a/server/apache/mirrormanager.conf b/server/apache/mirrormanager.conf
index 012ab48..d3852b9 100644
--- a/server/apache/mirrormanager.conf
+++ b/server/apache/mirrormanager.conf
@@ -4,7 +4,7 @@ Alias /mirrormanager/crawler /var/log/mirrormanager/crawler
WSGISocketPrefix /var/run/mirrormanager/wsgi
WSGIRestrictSignal Off
-WSGIDaemonProcess mirrormanager user=mirrormanager group=mirrormanager
display-name=mirrormanager maximum-requests=1000 processes=2 threads=1 umask=0007
+WSGIDaemonProcess mirrormanager user=mirrormanager group=mirrormanager
display-name=mirrormanager maximum-requests=1000 processes=4 threads=1 umask=0007
WSGIPythonOptimize 1
WSGIScriptAlias /mirrormanager
/usr/share/mirrormanager/server/mirrormanager.wsgi/mirrormanager
Show replies by date