google / google/leveldb

Re-compute / pre-populate compaction heuristics when log/manifest reuse is turned on.

Open
#794 1 comment 1 reaction 0 assignees View on GitHub
bug
Dominant language
C++
Stars
39.4k
Forks
8.2k
PR merge metrics
No merged PRs in 30d

Description

When the log/manifest reuse option is turned on (I forget the specific name, where the log is just loaded into memory and there isn't a repair/compaction), compaction heuristics aren't appropriately set. This means that if a user opens the database, writes up to right 'before' compaction would trigger, and then closes & re-opens the database (and repeats), there is a never-ending growing log file w/o any compaction until OOM.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.