Suspicious memory leak (Segment snapshot of DT_SnapshotOfRead)
Open
Nobody has claimed this yet.
component/storage
severity/moderate
type/bug
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
all snapshot can be released after the query/compaction task finished
3. What did you see instead (Required)
There is no suspicious deadlocks stack frame: tiflash_pid.zip
From the metrics, we can see that
- the oldest snapshot lifetime is more than 2 days
- all created snapshots can be released and the min count down to 0, except the min num of
DT_SnapshotOfReadis 15
4. What is your TiFlash version? (Required)
v5.4.0
Contributor guide
No contributing guide indexed for this repository
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 tiflash_pid.zip and the snapshot metrics for TiFlash v5.4.0, focusing on why 15 DT_SnapshotOfRead snapshots remain after query or compaction work finishes. Done means reproducing the condition and confirming that all snapshots are released and the minimum count returns to zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100