batch on delete cause the resolved-ts spikes and tikv-cdc memory quota full
Open
Nobody has claimed this yet.
severity/moderate
type/enhancement
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
- insert many rows into the upstream tidb cluster.
- run the following sql
batch on test.bank0.id limit 20000 delete from test.bank0;
The resolved-ts increase a lot, and TiKV-CDC memory quota also increase, implies that the TiCDC cannot consume data in time.
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
Reproduce the reported behavior in a TiDB cluster using the provided INSERT steps and batch on test.bank0.id limit 20000 delete from test.bank0 statement. Observe resolved-ts and TiKV-CDC memory quota while the delete runs; the issue does not specify a target fix or completion criterion, so those must be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100