After the cdc master and backup are synchronized with the normal table, the cpu keeps rising and does not fall.
Open
Nobody has claimed this yet.
contribution
first-time-contributor
type/bug
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What did you do?
Configure CDC tasks, including sending information to downstream pulsar and tidb
What did you expect to see?
I expect to see normal CPU drops
What did you see instead?
- v8.5.3
profiling_2025-12-29_15-59-00.zip
- v8.5.3
profiling_2025-12-29_16-04-45.zip
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
v8.5.2,v8.5.3
Upstream TiKV version (execute tikv-server --version):
v8.5.2,v8.5.3
TiCDC version (execute cdc version):
v8.5.2,v8.5.3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the attached profiling archives for v8.5.2 and v8.5.3 alongside the CDC task configuration described in the report. Compare CPU activity after the CDC master and backup synchronize with the normal table; done means the cause is identified and CPU returns to normal after synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100