TiCDC handles DDLs one by one, which could be a bottleneck #11467
Labels
affects-5.4
affects-6.1
affects-6.5
affects-7.1
affects-7.5
affects-8.1
area/ticdc
Issues or PRs related to TiCDC.
report/customer
Customers have encountered this bug.
type/enhancement
The issue or PR belongs to an enhancement.
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)
The text was updated successfully, but these errors were encountered: