happyboy1024 opened a new issue, #5654: URL: https://github.com/apache/seatunnel/issues/5654
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened I stopped a synchronization task by triggering savepoint. I then try to recover the task from savepoint, and I expect the task to continue running where it stopped until all the data is synchronized. However, I found that after the task was restored, no data was written and the task ended quickly. I checked the problem and found that due to the execution order of the tasks, the pending split would be extracted by **map.remove()** and assigned to the corresponding SourceReader. However, the current SourceReader is not yet registered with the environment, resulting in the loss of these pending split. ### SeaTunnel Version 2.3.3 ### SeaTunnel Config ```conf env { job.mode=BATCH job.name=DEMO } source { Jdbc { url="jdbc:mysql://xxxx/transfer_source" driver="com.mysql.cj.jdbc.Driver" user="root" password="xxxx" query="select * from order_info" partition_column=id partition_num=20 parallelism=2 } } transform { } sink { Jdbc { url="jdbc:mysql://xxxx/transfer_sink?rewriteBatchedStatements=true" driver="com.mysql.cj.jdbc.Driver" user="root" password="xxxx" database="transfer_sink" table="order_info_sink" batch_size=1000 enable_upsert=true generate_sink_sql=true primary_keys = [id] query = "" } } ``` ### Running Command ```shell ./bin/seatunnel-local.sh -c config/savepoint.config ./bin/seatunnel-local.sh -s {jobid} ./bin/seatunnel-local.sh -c config/savepoint.config -r {jobid} ``` ### Error Exception ```log no exception ``` ### Zeta or Flink or Spark Version Zeta ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
