DanielLeens commented on issue #10061: URL: https://github.com/apache/seatunnel/issues/10061#issuecomment-5111116917
I rechecked this old Kafka transaction issue against the current repository state. The specific failure described here appears to have been covered by PR #10013, which is now merged. In current `dev`, `KafkaTransactionSender.abortTransaction(long checkpointId)` reinitializes the transaction id for each checkpoint id before checking the producer epoch, so the old loop is no longer the same as the original report. Because there has not been a new reproduction after #10013 merged, I think this issue can be closed for the current `dev` line. If someone can still reproduce it on a current release or current `dev`, please add a fresh update with: 1. the exact SeaTunnel version / commit; 2. the Kafka broker version and transaction timeout settings; 3. the checkpoint id sequence being aborted; 4. the SeaTunnel task log around restore and abort; 5. the relevant broker-side transaction coordinator log. With that information we can tell whether it is a regression beyond #10013 or a release-line/backport question for older 2.3.x deployments. -- 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]
