Doooing opened a new issue, #8301: URL: https://github.com/apache/seatunnel/issues/8301
### 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 st-2.3.8 使用 jdbc source 读取源端 oracle/mysql/pg 数据时, 会自动获取源端表主键, 并根据主键自动切块. 但如果主键类型为 string 则切块这个过程会非常慢, 会导致大批量 st 任务阻塞. 对于 st-2.3.3 版本来说, 没有根据主键自动切块这一步骤, 因此 2.3.3 版本执行正常. St-2.3.8 When using jdbc source to read the source oracle/mysql/pg data, it will automatically obtain the primary key of the source table and automatically cut blocks according to the primary key. However, if the primary key type is string, the blocking process will be very slow, which will cause a large number of st tasks to be blocked. For st-2.3.3 version, there is no automatic block cutting step according to the primary key, so version 2.3.3 executes normally. ### SeaTunnel Version 2.3.8 ### SeaTunnel Config ```conf There is no problem with the configuration file ``` ### Running Command ```shell There is no problem with the Running Command ``` ### Error Exception ```log 从 st server 和 st client 的日志来看, 一切都在正常运行流程中, 只是切块耗费大量时间, 导致后续的 st 表同步任务无法执行. 期间没有任何异常报错的输出, 只是开启 debug 之后会发现, 源端主键为 string 类型的表数据抽取阶段会卡在 split chunk 上. Judging from the logs of st server and st client, everything is in the normal process, but it takes a lot of time to cut blocks, resulting in the inability to perform subsequent st table synchronization tasks. There is no abnormal error output during this period, but after turning on the debug, you will find that the table data extraction stage of the source primary key is string type will be stuck on the split chunk. ``` ### Zeta or Flink or Spark Version _No response_ ### 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]
