TiDB v6.5 DDL job is always in the cancelling state, how to completely terminate the DDL?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb v6.5 DDL job一直处于cancelling状态,请问怎样彻底结束该ddl

| username: 张小凉1

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.5
[Reproduction Path] Executing ALTER TABLE ‘table’ ADD ‘column’ DATETIME(6) DEFAULT NULL; got stuck, directly canceled execution. Later, multiple retries failed to modify the table structure, resulting in an error.

I want to ask how long it generally takes to kill the canceled DDL? Or is there any other way to completely terminate the DDL?

[Attachment: Screenshot/Log/Monitoring]

| username: kkpeter | Original post link

Restart the TiDB node

| username: xingzhenxiang | Original post link

Shouldn’t adding a column be instantaneous?

| username: tidb菜鸟一只 | Original post link

It should be fast normally.

| username: liuis | Original post link

Adding a column should be completed quickly, right?

| username: Kongdom | Original post link

Try restarting the TiDB node. However, generally adding a field should be quite fast.

| username: 胡杨树旁 | Original post link

Will restarting the TiDB node solve this problem? I have always been unclear whether I need to restart the TiDB node or the TiKV node. DDL seems to be persisted on the TiKV node, and TiDB, as the owner, executes the DDL.