Fix uWSGI configuration to handle write errors and optimize performance

mjanez · Oct 8, 2024 · 52a80e4 · 52a80e4
1 parent 380abfb
commit 52a80e4
Showing 1 changed file with 5 additions and 2 deletions.
diff --git a/ckan/setup/start_ckan.sh.override b/ckan/setup/start_ckan.sh.override
@@ -57,8 +57,11 @@ chown -R ckan:ckan $CKAN_LOGS_PATH/xloader
 # Set the common uwsgi options. 
 ## Add thunder-lock to prevent multiple workers from running the same job and buffer-size to prevent large headers
 ## To increase performance, you can adjust the number of processes (-p) (More info: https://uwsgi-docs.readthedocs.io/en/latest/Options.html & https://www.bloomberg.com/company/stories/configuring-uwsgi-production-deployment/)
+# Fix uWSGI raises OSError: write error: https://stackoverflow.com/a/45393743
 UWSGI_OPTS="--thunder-lock \
             --ignore-sigpipe \
+            --ignore-write-errors \
+            --disable-write-exception \
             --socket /tmp/uwsgi.sock \
             --wsgi-file /srv/app/wsgi.py \
             --module wsgi:application \
@@ -71,8 +74,8 @@ UWSGI_OPTS="--thunder-lock \
             --harakiri $UWSGI_HARAKIRI \
             --max-requests 500 \
             --max-worker-lifetime 3600 \
-            --reload-on-rss 1024 \
-            --processes 2 \
+            --reload-on-rss 2048 \
+            --processes 4 \
             --buffer-size 32768 \
             --disable-logging \
             --log-4xx \