Open dibrother opened 3 weeks ago
The current version being used is 2.3.7.
Maybe you're using the wrong snapshot. Has the table structure changed before and after the snapshot you are using?
The source table structure has been changed (deleting a field), will this affect the recovery? The change of upstream data is uncontrollable.
We will fix the problem in this pr. https://github.com/apache/seatunnel/pull/7463.
Thank you very much, looking forward to future versions.
Search before asking
Description
Simulate power outage,when I kill all seatunnel processes, I am unable to recover jobs based on the checkpoint. When the cluster node is restarted, all previously run tasks are not automatically restored.
1.Deploy SeaTunnel Engine In Separated Cluster Mode, all on the same server
2.Starting the SeaTunnel Engine Master Node 3.Starting The SeaTunnel Engine Worker Node 4.Submitting Jobs
5.Full data extraction and normal synchronization
recovery: 1.Starting the SeaTunnel Engine Master Node 2.Starting The SeaTunnel Engine Worker Node 3.Resuming Jobs
report errors:
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct