amoro: [Bug]: Optimizing process stuck after a few failures
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.
Affects Versions
0.5.1
What engines are you seeing the problem on?
AMS, Optimizer
How to reproduce
- create a table with some data that meets the optimizing conditions.
- truncate a data file that would take part in the optimizing compaction.
- AMS tries to optimize the table but fails and retries.
- 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?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project’s Code of Conduct
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 35 (35 by maintainers)
For me, this is why the state is not being updated.