tiflow
tiflow copied to clipboard
TiCDC handles DDLs one by one, which could be a bottleneck
What did you do?
Deploy a TiCDC cluster, and run lots of TRUNCATE
statements in the upstream TiDB.
What did you expect to see?
No response
What did you see instead?
TiCDC handles DDLs one by one. It slows down the replication.
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version();
in a MySQL client):
(paste TiDB cluster version here)
Upstream TiKV version (execute tikv-server --version
):
(paste TiKV version here)
TiCDC version (execute cdc version
):
(paste TiCDC version here)