On this page
Kill the connection on the specified thread.
KILL CONNECTION <internal_process_id> [<node_id>]KILL QUERY <query_id> [<node_id>]
internal_- ID of the thread to kill.
query_- ID of the query to kill.
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.
You can query the
information_table for the required parameter values, where the
schema. MV_ PROCESSLIST
IDfield in the table contains the thread/query ID and the
NODE_field contains the ID of the node.
internal_- ID of the thread to kill, which can be found by running SHOW_
process_ id PROCESSLIST.
KILL CONNECTIONwill disconnect the client associated with
process_ id This is the default, meaning that running
KILL <>will have the same result.
KILL QUERYallows you to kill a query running on any aggregator in the cluster.
KILL QUERYwill not disconnect the client associated with
process_ id Instead, the client will receive an error.
Any query running on the connection will be rolled back.
SingleStoreDB 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.
This command should be run on the master aggregator or a child aggregator node (see Node Requirements for SingleStoreDB Commands).
Refer to the Permission Matrix for the required permission.
KILL CONNECTION 3123;Query OK, 0 rows affected (0.00 sec)
Last modified: January 9, 2023