MySQL Processes

MySQL Processes is a root-administrator page for reviewing active MySQL/MariaDB threads and terminating a problematic database connection when it is clearly safe to do so.

Where to find it: Open the Server menu and choose MySQL Processes. Conditional items appear only when their service is installed and available.

Available to: Root only.

What this page does

The page is an incident and performance tool, not a database-creation page. It shows live database activity so administrators can identify long-running queries, locked or sleeping sessions, busy hosts, affected databases, and processes that may need to be stopped during troubleshooting.

Before you start

MySQL Processes is an evidence page. Refresh it in the correct scope and correlate the result with the owning service or logs before using a disruptive action.

Why use it — and when not to

Use MySQL Processes when you need current evidence or a bounded status view. Do not use one snapshot as the only basis for a destructive action; correlate it with time, scope, logs, and the affected service.

How to use it

1. Choose the exact account, domain, service, process, or time range.
2. Refresh the data and read the status in context.
3. Correlate it with logs or a second status source before taking action.
4. If an action is needed, use the smallest supported action and refresh again.

Result and next check

Opening or refreshing MySQL Processes does not change configuration. If the page offers an action such as kill, clear, retry, or restart, that action has its own impact and must be confirmed separately.