redo apply oom
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What did you do?
Run cdc redo apply
https://tcms.pingcap.net/dashboard/executions/plan/8231722
What did you expect to see?
No response
What did you see instead?
CDC OOM
["run redo cmd finished"] [result=null] [error="command terminated with exit code 137"]
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)
Upstream TiKV version (execute tikv-server --version):
(paste TiKV version here)
TiCDC version (execute cdc version):
master
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 reproducing cdc redo apply using the linked execution plan and collect the missing TiDB, TiKV, and TiCDC version details. Trace the TiCDC redo apply entry point to determine where memory use leads to exit code 137; done means the OOM cause is identified and the command completes without termination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100