Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TiCDC 同步数据到Kafka，上下游事务顺序不一致问题
|
username: ORA-600
Bug Report
TiCDC 6.5.6 synchronizes data to downstream Kafka, resulting in inconsistent transaction order between upstream and downstream.
The upstream TiDB database performs an insert operation on the xxx_lesson table first, followed by an update operation (not in the same transaction as the insert). The downstream Kafka receives the messages in the order of update first, then insert.
Specific TiCDC task parameter configuration:
tiup ctl:v6.5.6 cdc changefeed create protocol=canal-json&enable-tidb-extension=false&transaction-atomicity=none&content-compatible=true
[TiDB Version]
TiDB 6.5.6
[Impact of the Bug]
Inconsistent transaction order between upstream and downstream
[Possible Steps to Reproduce the Issue]
[Observed Unexpected Behavior]
Inconsistent transaction order between upstream and downstream
[Expected Behavior]
Consistent transaction order between upstream and downstream
[Related Components and Specific Versions]
TiDB 6.5.6, TiCDC 6.5.6
[Other Background Information or Screenshots]