[Bug]: Data inconsistency caused by switching between primary and backup nodes

[CatchYouIfICan]

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

• [x] I agree to follow this project's Code of Conduct

[klion26]

Seems that node1 can't update the optimizing status after it becomes a follower?

[zhangwl9]

I would like to take this issue. Please assign it to me. @zhangwl9

[klion26]

@zhangwl9 You can comment a single take in the comment to have the issue assigned to yourself now

[CatchYouIfICan]

Seems that node1 can't update the optimizing status after it becomes a follower?

Because the thread will continue to complete unfinished work before completely exiting.