tiflow
tiflow copied to clipboard
Conflict detector doesn't seperate Txns into different table space
What did you do?
Starts a changefeed with many tables.
What did you expect to see?
No response
What did you see instead?
Conflict detector doesn't seperate Txns into different table space, which may cause wrong dependencies between Txns from different tables. This may reduce sink throughput.
Here is a result. We can see conflict detect duration is very high:
Versions of the cluster
TiCDC 6.5.9 and all later versions.