google / google/leveldb

[Not an issue] What happens when you try to write and the disk is full

Open
#870 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
39.4k
Forks
8.2k
PR merge metrics
No merged PRs in 30d

Description

Recently i had this error on a project of mine, and now i cannot find a lot of keys (181k keys). If the disk gets full is there a chance of losing keys during a compact or something like that? How can i mitigate this issue in the future? (besides buying more disk space ofc)

Contributor guide

Open the contributing guide

Research direction

The issue names no file, test, or entry point. Start by reviewing LevelDB's documented disk-full and compaction behavior; done would be a clear, supported explanation of the reported risk and available mitigation guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
databases
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.