Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

The AMS inserts records into the optimizing_process_state table at the start of each optimizing process, including a memory-consuming rewriteInput field of type longblob. This field can consume significant storage from several MB to GB, especially as the number of tasks increases.

Upon investigation, we found that the rewriteInput field is only needed for restoring tables that were abnormally interrupted but remain in the optimizing state. Once the optimizing process is successfully completed, retaining this large field is unnecessary and leads to excessive storage consumption.

Therefore, clearing this data after optimizing can help reduce storage usage and improve system performance.

How should we improve?

Remove unnecessary records in table optimizing_process_state when completing optimizing.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

• I agree to follow this project's Code of Conduct