The job is stuck and unresponsive, and after canceling it, the subsequent jobs still cannot run

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

Original topic: job卡死一直没有反应,然后把它cancel后,接下来的job还是无法运行

| username: TiDBer_7Q5CQdQd

Over 40 million records, deleting one field, 24GB of memory remaining.

| username: RenlySir | Original post link

Cancel everything and start over?
Also, check the TiDB monitoring? Investigate why it’s stuck? Are the resources being heavily utilized?

| username: redgame | Original post link

What is this job about?

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

Canceling means it is in the process of being canceled, not successfully canceled. If it is really urgent, you can try restarting the tidb-server.

| username: 像风一样的男子 | Original post link

Execute after canceling is finished.

| username: tony5413 | Original post link

What job is it? Does it need optimization?

| username: zhanggame1 | Original post link

How much data is in the table where you added the column, and how long did you wait? This operation is very slow with large amounts of data.

| username: TiDBer_7Q5CQdQd | Original post link

This dataset has over 40 million records. Deleting a field has no response. There are still 24GB of memory left.

| username: h5n1 | Original post link

Check if this view has any content: mysql.tidb_mdl_view