TiDB Work Order Stuck and Unable to Execute

Translated
1

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

Original topic: tidb工单卡住无法执行

| username: tidb狂热爱好者

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] 6.3
We installed version 6.3 of TiDB in a pre-release environment.
This version has a feature where MAX_execution_time affects DDL. Previously, it did not.
Now, this causes any DDL-related tickets submitted through Yearning to fail to execute. Is there any way to solve this? For example, using a hint with alter table to change the execution time would work. I tried placing
set session max_execution_time=0; at the beginning, but it had no effect.
[Reproduction Path] What operations were performed that led to the issue
[Encountered Issue: Problem Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: 啦啦啦啦啦 | Original post link

This is not a feature unique to version 6.3; it has been effective for DDL in earlier versions. The command set session max_execution_time=0; having no effect makes me suspect that the DDL and the set command are not executed in the same session. You might consider changing the execution logic in the yearning code.

3
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.