DanielLeens commented on issue #12212: URL: https://github.com/apache/seatunnel/issues/12212#issuecomment-5584873523
Thanks for the detailed report. The stack trace establishes that the failure occurs in the MySQL binlog row-event decoder below the SeaTunnel CDC reader. Current `dev` still packages Debezium 1.9.8.Final for the MySQL CDC connector and carries a local buffered-socket workaround from #7380; I found no matching open fix PR or recent `dev` change for this EOF path. That is not enough to attribute the EOF to SeaTunnel itself, a source-server/binlog compatibility case, or the upstream decoder. The reported source is SeaTunnel 2.3.13, so please first capture a minimally redacted reproducer against a current supported release or `dev`. To make the result actionable, please also provide: 1. the source server product and exact version (including whether it is MySQL-compatible rather than MySQL), plus `binlog_format`, `binlog_row_image`, checksum, GTID, and server time-zone settings; 2. the `SHOW CREATE TABLE` output and any DDL/schema change around the failing position for each affected table, especially the `DATETIME_V2` column; 3. the exact binlog file/position or GTID before and after the failed event, together with a safely redacted `mysqlbinlog --base64-output=DECODE-ROWS -vv` excerpt sufficient to identify the event shape; 4. the MySQL-CDC plugin/dependency versions actually shipped in the submitted distribution; and 5. the checkpoint/restore offset and the primary keys plus source/target observations for the two rows said to be absent. Please do not post raw binlog data or sensitive values. With those artifacts, we can replay the event on `dev` and distinguish a decoder failure from the recovery/target-observation boundary before proposing a fix. -- 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]
