• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Question Scoreboard full and/or max request workers limit

kevinjansen

Basic Pleskian
Server operating system version
Almalinux 8
Plesk version and microupdate number
18.0.60
Hi All,

I am wondering if there is a max limit a domain can use so we can prevent that a single domain can bring down a server.

We are now seeing sometimes:

server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
or
scoreboard is full, not at MaxRequestWorkers

The config is:

<IfModule mpm_event_module>
LoadModule cgid_module modules/mod_cgid.so
MaxRequestWorkers 2000
ServerLimit 100
</IfModule>

This is a 12 Core and 48GB server. And when you check the /server-status page its always 1 domain that fills up the entire scoreboard.
I like to find a way (if possible) to prevent that a single domain can bring down a server. We have already capped the max memory limit and cpu cores, but the problem is now moving towards the scoreboard.

So is there a option to say for example a domain is only able to use 200 out of that 2000 workers (10%).
Or how do others prevent that a single domain can bring down a server.

Kind regards,

Kevin
 
Back
Top