copr: workaround memory leak

/api_3/package/list/ is leaking a memory. Even after two days of investigation, I did not find why.
Just recycle it more frequent to avoid oomkiller.
This commit is contained in:
Miroslav Suchý 2021-04-19 16:03:25 +02:00
parent 8ccd038356
commit 08b2e1370e

View file

@ -4,6 +4,7 @@ Alias "/db_dumps/" "/var/www/html/db_dumps/"
WSGIDaemonProcess 127.0.0.1 user=copr-fe group=copr-fe processes=4 threads=5 display-name=other maximum-requests=8000 restart-interval=300 graceful-timeout=20
WSGIDaemonProcess api user=copr-fe group=copr-fe processes=2 threads=15 display-name=api maximum-requests=8000 graceful-timeout=20
WSGIDaemonProcess api-memory-leak user=copr-fe group=copr-fe processes=2 threads=1 display-name=api-memory-leak maximum-requests=10 graceful-timeout=20
WSGIDaemonProcess backend user=copr-fe group=copr-fe processes=2 threads=15 display-name=backend maximum-requests=8000 graceful-timeout=20
WSGIDaemonProcess stats user=copr-fe group=copr-fe processes=2 threads=15 display-name=stats maximum-requests=8000 graceful-timeout=20
WSGIDaemonProcess tmp user=copr-fe group=copr-fe processes=2 threads=15 display-name=tmp maximum-requests=8000 graceful-timeout=20
@ -71,6 +72,9 @@ WSGIApplicationGroup %{GLOBAL}
<LocationMatch "^/api.*upload.*">
WSGIProcessGroup upload
</LocationMatch>
<LocationMatch "^/api_3/package/list.**">
WSGIProcessGroup api-memory-leak
</LocationMatch>
<LocationMatch "^/coprs.*new_build_upload.*">
WSGIProcessGroup upload
</LocationMatch>