liangcw1111 opened a new issue, #8379: URL: https://github.com/apache/seatunnel/issues/8379
### 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 When maxcompute source split enumerator assign pending splits, the assignSplitOperation is sent to task group worker and source reader execute pollNext(Collector<SeaTunnelRow> output) completed, if split enumerator signalNoMoreSplits Operation is not arrived, the pollNext(Collector<SeaTunnelRow> output) may execute again. This leads to the set of splits read more than once. It is easy to hanpened when the cluster's system load is high. ### SeaTunnel Version 2.3.7 ### SeaTunnel Config ```conf seatunnel: engine: classloader-cache-mode: true history-job-expire-minutes: 1440 backup-count: 1 print-execution-info-interval: 60 print-job-metrics-info-interval: 60 queue-type: blockingqueue slot-service: dynamic-slot: false slot-num: 20 checkpoint: interval: 30000 timeout: 2147483647 max-concurrent: 5 tolerable-failure: 2 storage: type: oss ``` ### Running Command ```shell sh /alidata1/za-seatunnel/seatunnel-2.3.7/bin/seatunnel-cluster.sh -d -r master/worker ``` ### Error Exception ```log There is no exception, but the data of one or more splits is reading repeated. ``` ### Zeta or Flink or Spark Version zeta ### Java or Scala Version java 1.8 ### Screenshots _No response_ ### Are you willing to submit PR? - [X] 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]
