ydb-platform / ydb-platform/ydb
Architectural question about data tablet storage and dsproxy lack of delete operation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.8k
- Forks
- 820
- Avg merge
- 16h 50m
- Merged PRs (30d)
- 734
Description
I'm trying to get a better high level understanding on how ydb works and from what I understand so far all writes from data tablets go through dsproxy and I can't find there a delete operation. Only put/get/block/gc. Do I correctly understand that data tablets periodically re-write their entire data set and the gc the old snapshot(s)?
Would be cool to have some short docs through the codebase :)
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 reading the dsproxy operations named in the issue—put, get, block, and gc—and trace how data tablets write and reclaim older snapshots. Document whether data tablets rewrite their full dataset and use gc for old snapshots, then add the requested short explanation through the codebase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100