-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Closed
Labels
affects-6.5This bug affects the 6.5.x(LTS) versions.This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.component/CDCComponent: Change Data CaptureComponent: Change Data Captureseverity/moderatetype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.
Description
Bug Report
What version of TiKV are you using?
v6.5.5.
However, I guess the issue also exists in all later versions.
What operating system and CPU are you using?
Doesn't matter.
Steps to reproduce
It can't be reprocued stably. The root cause is still unknown.
What did you expect?
TiCDC incremental scan shouldn't be too slow.
What did happened?
TiCDC incremental scan is too slow (about 30min), and incremental scan worker CPU usage is always 100%:
[2023/11/27 10:54:58.200 +08:00] [INFO] [replication_manager.go:635] ["schedulerv3: slow table"] [namespace=default] [changefeed=policy-t2o-36] [tableID=52592] [tableStatus=] [checkpointTs=445920115528303141] [resolvedTs=445920115528303141] [checkpointLag=57m32.250351282s]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
affects-6.5This bug affects the 6.5.x(LTS) versions.This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.component/CDCComponent: Change Data CaptureComponent: Change Data Captureseverity/moderatetype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.

