[Improvement]: Refactor the Optimizing page to support display of more Process types in the future. #3777
Description
Search before asking
- I have searched in the issues and found no similar issues.
What would you like to be improved?
Currently, the Optimizing page displays the information of all tables' Optimizing Processes at the table level. This design implicitly reflects an internal AMS implementation logic, each table can have only one active Optimizing Process at a time, and OptimizingStatus is not the status of the Process itself, but rather a table-level status.
Other maintenance actions in AMS—such as Expire Snapshot, currently have no way to be displayed on the frontend, even though they are just as important as file-compaction.
This issue aims to refactor the Optimizing-related pages by introducing a Processes view that breaks the “one-table-one-process” limitation and, in the future, display all maintenance operations (e.g., Expire Snapshot, Clean Orphan Files) as different Processes.
How should we improve?
First, the sidebar item “Optimizing” will be renamed to “Execution,” indicating that this section displays what AMS is currently running.
Second, the Tables tab will be retained; it will continue to present, at the table level, an aggregated view of each table’s currently active Processes and resource usage.
Finally, a new Processes tab will be introduced, listing all Active Processes—both the existing TableOptimizingProcess and any new Processes that represent table maintenance actions.
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