You can identify and terminate specific MySQL or MariaDB processes that are consuming excessive system resources. This task is performed by a Server Administrator within the WHM interface to maintain server stability.
Before you begin
You will need:
Root access to the WHM interface
A valid reason for terminating a process (e.g., a "stuck" query or a runaway process causing high CPU/memory usage)
Review and stop a MySQL process
Log in to WHM.
In the left-hand sidebar, search for Process Manager or navigate to Home » Server Information » Process Manager.
Locate the list of active processes.
Use the filter or search bar to find the specific MySQL or MariaDB process.
Identify the process by its PID (Process ID) or the query it is currently executing.
Select the process and click Kill or Stop.
Warning: Terminating a MySQL process will immediately stop the query that the process is running. If the process is part of a critical database operation, such as a large import or a complex update, the operation will be interrupted and may leave the database in an inconsistent state.
Confirm the result
The process will no longer appear in the Process Manager list.
The system's CPU or memory usage should decrease as the specific process is released.
If a process remains active after a kill command
If a process does not disappear from the list immediately after a kill command, it may be stuck in a "zombie" state or waiting on an I/O operation.
Wait 60 seconds and refresh the Process Manager page.
If the process persists, it may require a restart of the MySQL service to clear from the system memory.
If a service restart is required, navigate to Home » Server Information » Restart Services and select Graceful Restart for MySQL.
Limitations
This procedure only stops the specific process identified; it does not restart the entire MySQL service.
Terminating a process during a heavy write operation can result in table locks or data inconsistencies.
This action does not resolve the underlying issue that caused the process to run poorly; it only addresses the immediate resource consumption.
