The SeaTunnel job designed for real-time data extraction from MySQL to StarRocks stalled after starting, showing zero read and write counts. After running for six hours, it terminated due to a checkpoint timeout error. The analyzed MySQL table lacked auto-increment primary keys, differing from previously successful tables which had them. SeaTunnel's syncing process includes a snapshot phase first, which seems to be where the job is stuck. Documentation offers configurable parameters, though they do not clarify the architectural aspects of snapshot sync.
"SeaTunnel utilizes a two-step approach for syncing data, comprising an initial snapshot sync followed by a binlog-based incremental sync, which is sensitive to primary key configurations."
"The job showed zero read and write counts, indicating a halt during the snapshot phase. This may relate to MySQL tables lacking auto-increment primary keys."
Read at Hackernoon
Unable to calculate read time
Collection
[
|
...
]