-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cdc goroutines become crazy when initializing a capture with lots of regions and tikv.cdc.min-ts-interval = 200ms #5610
Comments
close pingcap#5610 # Conflicts: # cdc/kv/client.go # cdc/kv/region_worker.go
close pingcap#5610 # Conflicts: # cdc/kv/client.go # cdc/kv/region_worker.go
close pingcap#5610 # Conflicts: # cdc/kv/client.go # cdc/kv/region_worker.go
/label affect-5.4 |
@nongfushanquan: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/label affects-5.4 |
What did you do?
Create a capture on 16 MySQL tables, 131K regions totally with
What did you expect to see?
Both 2 operations can be finished quickly. With
tikv.cdc.min-ts-interval = 1s
it's expected:What did you see instead?
However with
tikv.cdc.min-ts-interval = 200ms
the capture creating can never finished, and cpu usage is very high:And here is a 30s CPU profile:
We can see the CPU time is about 480s, which means all 16C are very busy on
runtime.selectgo
.Versions of the cluster
All components are nightly.
Go version is 1.18.1.
Investigations
The text was updated successfully, but these errors were encountered: