Skip to content

Commit

Permalink
add KILL statement can kill DDL jobs describe (#16124) (#16354)
Browse files Browse the repository at this point in the history
  • Loading branch information
ti-chi-bot authored Jan 29, 2024
1 parent 2dfca01 commit f940c11
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion sql-statements/sql-statement-admin-cancel-ddl.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ If the operation fails to cancel the jobs, specific reasons are displayed.

> **Note:**
>
> - Only this operation can cancel DDL jobs. All other operations and environment changes (such as machine restart and cluster restart) cannot cancel these jobs.
> - Before v6.2.0, only this operation can cancel DDL jobs, and all other operations and environment changes (such as machine restart and cluster restart) cannot cancel these jobs. Starting from v6.2.0, [`KILL`](/sql-statements/sql-statement-kill.md) statements can also be used to cancel ongoing DDL jobs by killing them.
> - This operation can cancel multiple DDL jobs at the same time. You can get the ID of DDL jobs using the [`ADMIN SHOW DDL JOBS`](/sql-statements/sql-statement-admin-show-ddl.md) statement.
> - If the jobs you want to cancel are finished, the cancellation operation fails.
Expand Down
2 changes: 1 addition & 1 deletion sql-statements/sql-statement-kill.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ summary: An overview of the usage of KILL for the TiDB database.

# KILL

The `KILL` statement is used to terminate a connection in any TiDB instance in the current TiDB cluster.
The `KILL` statement is used to terminate a connection in any TiDB instance in the current TiDB cluster. Starting from TiDB v6.2.0, you can also use the `KILL` statement to terminate ongoing DDL jobs.

## Synopsis

Expand Down

0 comments on commit f940c11

Please sign in to comment.