KILL CONNECTION
On this page
Kill the connection on the specified thread.
Syntax
KILL CONNECTION <internal_process_id> [<node_id>]KILL QUERY <query_id> [<node_id>]
Arguments
-
internal_
- ID of the thread to kill.process_ id -
query_
- ID of the query to kill.id -
node_
- ID of the node (aggregator) on which the query/thread is running.id If the node_
is not specified, the query/thread running on the current node is killed.id Important
You can query the
information_
table for the required parameter values, where theschema. MV_ PROCESSLIST ID
field in the table contains the thread/query ID and theNODE_
field contains the ID of the node.ID
Remarks
-
internal_
- ID of the thread to kill, which can be found by running SHOW_process_ id PROCESSLIST. -
KILL CONNECTION
will disconnect the client associated withinternal_
.process_ id This is the default, meaning that running KILL <>
will have the same result. -
KILL QUERY
allows you to kill a query running on any aggregator in the workspace. -
KILL QUERY
will not disconnect the client associated withinternal_
.process_ id Instead, the client will receive an error. -
Any query running on the connection will be rolled back.
-
SingleStoreDB Cloud checks for the kill bit during any potentially long running loop during query execution and rolls back the query’s transaction if the kill bit is set.
-
Refer to the Permission Matrix for the required permission.
Example
KILL CONNECTION 3123;Query OK, 0 rows affected (0.00 sec)
Related Topics
Last modified: January 9, 2023