MySQL Governor ​
MySQL Governor throttles database usage per account, so one busy site cannot starve the whole server. It is a CloudLinux component and the page is available on CloudLinux servers.
Overview ​
URL: /admin/settings/mysql-governor
The page sits under Settings > Databases.

The page is a three-step wizard: Review, Install, Manage.
Before you install ​
Warning: Installing Governor replaces the stock database server with the matching CloudLinux build, and the database server is restarted as part of it. Databases are unavailable while that happens, so every site on the server is affected for the length of the restart. Do this in a maintenance window, not on a whim.
The review step states plainly what the install will do and in what order. Two things are worth knowing before you start:
- Every database is backed up first, and the backup is verified. If the backup fails, the install stops before anything is changed. This is the safety net, and it is why the first stage takes the longest on a server with large databases.
- No reboot is needed. The server stays up; the database service does not.
The installer output is shown as it runs, so you can follow the stage it is on rather than watching a spinner.
After it is installed ​
The Manage step reports whether Governor is running, once it is up.
Removing it ​
Removal has its own page at /admin/settings/mysql-governor/remove, and the output is streamed live there as well. Removing Governor is the same kind of change as installing it: the database server is replaced and restarted, so treat it with the same care.
Related pages ​
- CloudLinux - the rest of the CloudLinux integration.
- LVE Manager - per-account resource limits.
- Database Settings - the MariaDB configuration.
- Backups - the backups that protect the data Governor sits in front of.