[Bug]: Restarting AMS may cause the table to remain in the running state indefinitely and never transition to another status. #4041
Description
What happened?
After restarting the AMS pod, we found that some tables had actually completed the minor process, but their status remained as "minor" and would never change from this state.
Affects Versions
0.8.0
What table formats are you seeing the problem on?
Iceberg
What engines are you seeing the problem on?
Spark
How to reproduce
When the table is in the committing state and the AMS pod is restarted, there is a chance of encountering this issue.
Relevant log output
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