-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Support killing the running optimizing process #1862
Comments
Thank you for suggesting this improvement. 'kill optimizing' is a relatively important operations and maintenance requirement. Currently, the preliminary plan is to implement this function in the standard operations and maintenance instructions. You can follow it in this issue However, before that, should we provide other ways to solve such operations and maintenance problems? For example, providing a script to clean up optimizing processes and so on. @zhoujinsong |
From a product design perspective, I think providing a |
That's cool. But I prefer the |
This feature is valuable for external optimizers. I have implemented this part of the code logic as @wangtaohz mentioned, can you assign a subtask to me for contribution. |
1 similar comment
This feature is valuable for external optimizers. I have implemented this part of the code logic as @wangtaohz mentioned, can you assign a subtask to me for contribution. |
👍 @tcodehuber You can create your own subtask and describe your approach, and I can assist in assigning the subtask to you. |
Search before asking
What would you like to be improved?
Due to some historical reasons, for some tables with serious fragmentation, it may require a lot of resources to enable self-o
ptimize for the first time, and even cannot be merged or take a long time. We hope to kill or skip this optimize process
How should we improve?
No response
Are you willing to submit PR?
Subtasks
Code of Conduct
The text was updated successfully, but these errors were encountered: