From aed3d479f004ec51a3016c44aa8638a6766b5854 Mon Sep 17 00:00:00 2001 From: Kevin Fenzi Date: Aug 31 2020 19:18:23 +0000 Subject: bodhi / base: change wsgi to only use 1 thread and more processes We are hitting odd db errors in bodhi frontend pods. See: https://pagure.io/fedora-infrastructure/issue/9234 It was suggested there to try moving threads down to 1 to avoid any possible threading concurrency issues. So this does that. It needs to be merged, then bodhi openshift playbook run and a new build/deployment rolled out. Signed-off-by: Kevin Fenzi --- diff --git a/roles/bodhi2/base/templates/httpd.conf.j2 b/roles/bodhi2/base/templates/httpd.conf.j2 index 2e6baa9..b6c7a1e 100644 --- a/roles/bodhi2/base/templates/httpd.conf.j2 +++ b/roles/bodhi2/base/templates/httpd.conf.j2 @@ -61,7 +61,7 @@ Alias /static/v{{ bodhi_version.split('-')[0] }} /srv/bodhi/bodhi/server/static/ {% else %} Alias /static/v{{ bodhi_version.split('-')[0] }} /usr/lib/python3.8/site-packages/bodhi/server/static/ {% endif %} -WSGIDaemonProcess bodhi display-name=bodhi processes=2 threads=2 maximum-requests=500 home=/httpdir request-timeout=90 +WSGIDaemonProcess bodhi display-name=bodhi processes=4 threads=1 maximum-requests=500 home=/httpdir request-timeout=90 WSGIApplicationGroup %{GLOBAL} WSGISocketPrefix run/wsgi WSGIRestrictStdout Off