[NEW] more rocksdb options supporting for write stall needed
- Dominant language
- C++
- Stars
- 4.4k
- Forks
- 658
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 10
Description
In my tests, when I ran a new compaction strategy that combined an **automatic compation operation with a compaction checker**, MY disk space was blown up so fast that level5 reclamation was slow and my disk ran the risk of being full. If I change this to **auto compaction+cron compaction(hourly)**, it will trigger a write stall that usually lasts more than half an hour and performs poorly. When I read the log, I usually write stall because **level0FIleNum is too large**, so I set this parameter to a larger value. However, something new happens, such as **Estimated Pending compaction bytes**, so I want to change this parameter by changing the configuration file. It turns out that kVRocks is not currently supported, so more rockDB parameters need to be supported, not just this one, or have other good suggestions?thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating Kvrocks' RocksDB option and configuration handling, then compare supported write-stall settings with the requested level0FileNum and Estimated Pending compaction bytes options. Done criteria are not specified beyond supporting additional RocksDB parameters or providing another recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100