link3280 opened a new issue, #2623: URL: https://github.com/apache/amoro/issues/2623
### What happened? If an optimizing task fails constantly (e.g. because of corrupted files), the optimizing task would be stuck at the `RUNNING` state after a few retries, while the task has already failed at the optimizer side. <img width="1288" alt="截屏2024-03-11 16 55 27" src="https://github.com/NetEase/amoro/assets/13482005/d18f7a74-aa0e-4fcf-82b2-7fd5824b09db";> ### Affects Versions 0.5.1 ### What engines are you seeing the problem on? AMS, Optimizer ### How to reproduce 1. create a table with some data that meets the optimizing conditions. 2. truncate a data file that would take part in the optimizing compaction. 3. AMS tries to optimize the table but fails and retries. 4. after a few retries, AMS would lose track of the task, and leave the task stuck at RUNNING state. ### Relevant log output _No response_ ### Anything else _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's Code of Conduct -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
