rust-rocksdb / rust-rocksdb/rust-rocksdb
Explicit db.flush() does not work in OptimisticTransactionDB
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.2k
- Forks
- 874
- PR merge metrics
- No merged PRs in 30d
Description
Repro https://github.com/pragmaxim-com/rust-playground/commit/e5ec1c6956d8868a6e09257fc71fb40fada2bab4
db.flush call does not lead to new (the first) sst file being created ... not even after thread-sleep 10 seconds after commit or after flushing
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 with the reproduction commit linked in the issue and inspect how OptimisticTransactionDB invokes db.flush after commit. Reproduce the missing first SST-file behavior, including the reported 10-second sleep, and compare the result with the expected flush behavior. Done means an explicit flush creates the expected SST file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100