[Bug]: Data inconsistency caused by switching between primary and backup nodes #3752
Description
What happened?
During the primary backup switch, Amoro experienced a stuck table optimization task due to inconsistent data. The specific process is shown in the figure.
Affects Versions
0.8.x
What table formats are you seeing the problem on?
Iceberg
What engines are you seeing the problem on?
AMS
How to reproduce
No response
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