MV_BLOCKED_QUERIES
This view provides the aggregated replication status of each database in the cluster.
Column name | Description |
---|---|
| ID of the node running the blocked query. |
| ID of the blocked query. |
| The text of the blocked query. |
| ID of the node that is running the blocking query. |
| ID of the blocking query. |
| Information on the type of block. Could be |
| The text of the blocking query, or a description of the connection. For example: “open idle transaction”. |
Example mv_blocked_queries Results
NODE_ID | ID | QUERY_TEXT | BLOCKING_NODE_ID | BLOCKING_ID | BLOCKING_TYPE | BLOCKING_QUERY_TEXT |
---|---|---|---|---|---|---|
1 | 42 | insert into t values (1) | 1 | 17 | user transaction | open idle transaction |
Both id
and blocking_id
refer to the “id” from information_schema.processlist
. This means you can join information_schema.mv_blocked_queries
with information_schema.processlist
to get more detail about the blocked or blocking process.
Once you know the query or connection responsible for blocking, you can use KILLALL QUERIES or KILL CONNECTION to unblock your process.