post-crash-compaction-produces-irrecoverable-corruption

Status: OUT

A crash during compaction produces irrecoverable data loss: no implementation uses write-temp/fsync/rename for atomicity (Bitcask deletes before renaming, LSM lacks atomic rename), and the resulting file corruption is terminal because every reader halts at the first CRC failure with no resync or skip capability.

Justifications

non-atomic compaction + terminal corruption handling = crash during compaction is unrecoverable

Depends on (SL): compaction-lacks-crash-safety-across-implementations, corruption-is-terminal-across-all-readers

Depended on by

JSON