Incremental scan is restarted unexpectedly due to GC pause is too long #2375
Labels
area/ticdc
Issues or PRs related to TiCDC.
component/replica-model
Replication model component.
difficulty/hard
Hard task.
severity/major
subject/replication-interruption
Denotes an issue or pull request is related to replication interruption.
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
Replicating 200+ tables with two TiCDC nodes. The initial incremental scan processes about 400G.
We found a capture is paused by GC too long, and triggers unexpected errors like
grpc keepalive dog timeout
and[pd] cannot update leader
, one of these errors cause capture exitscapture session done, capture suicide itself
and interrupts incremental scan.No capture exits and incremental scan interruption.
capture exits and incremental scan interruption.
Release-4.0 5a78519
The text was updated successfully, but these errors were encountered: