You are viewing an older version of this section. View current production version.
Kill the connection on the specified thread. Rolls back any query running on the thread.
KILL CONNECTION <internal_process_id> [<node_id>] KILL QUERY <query_id> [<node_id>]
internal_process_id- ID of the thread to kill.
query_id- ID of the query to kill.
node_id- ID of the node (aggregator) on which the query/thread is running. If the
node_idis not specified, the query/thread running on the current node is killed.Info
You can query the
information_schema.MV_PROCESSLISTtable for the required parameter values, where the
IDfield in the table contains the thread/query ID and the
NODE_IDfield contains the ID of the node.
internal_process_id- ID of the thread to kill, which can be found by running SHOW_PROCESSLIST.
KILL CONNECTIONwill disconnect the client associated with
internal_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
internal_process_id. Instead, the client will receive an error.
- Any query running on the connection will be rolled back.
- MemSQL 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 MemSQL Commands).
memsql> KILL CONNECTION 3123; Query OK, 0 rows affected (0.00 sec)