• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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