copr: repo files can eat whole pool, use dedicated ProcessGroup for them
Sometimes webUI lagged. When I checked I seen a lot of /coprs/ibotty/prometheus-exporters/repo/epel-7/ibotty-prome Those requests can be valid, but as there is many of them, they blocks processes handling webUI. Lets move /repo/ requesto to dedicated group.
This commit is contained in:
parent
229c81e31a
commit
58b7c91023
2 changed files with 4 additions and 0 deletions
|
@ -8,6 +8,7 @@ WSGIDaemonProcess api user=copr-fe group=copr-fe threads=15 display-name=api max
|
|||
WSGIDaemonProcess backend user=copr-fe group=copr-fe threads=15 display-name=backend maximum-requests=8000 graceful-timeout=20
|
||||
WSGIDaemonProcess stats user=copr-fe group=copr-fe threads=15 display-name=stats maximum-requests=8000 graceful-timeout=20
|
||||
WSGIDaemonProcess tmp user=copr-fe group=copr-fe threads=15 display-name=tmp maximum-requests=8000 graceful-timeout=20
|
||||
WSGIDaemonProcess repo user=copr-fe group=copr-fe threads=15 display-name=repo maximum-requests=8000 graceful-timeout=20
|
||||
WSGIScriptAlias / /usr/share/copr/coprs_frontend/application
|
||||
|
||||
<VirtualHost *:80>
|
||||
|
|
|
@ -34,6 +34,9 @@
|
|||
<Location /tmp>
|
||||
WSGIProcessGroup tmp
|
||||
</Location>
|
||||
<LocationMatch "/repo/">
|
||||
WSGIProcessGroup repo
|
||||
</LocationMatch>
|
||||
|
||||
#ErrorLog logs/error_coprs
|
||||
#CustomLog logs/access_coprs common
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue