facebook / facebook/rocksdb

Schedule Lmax compactions after releasing snapshots holding range tombstones

Open
#4,809 0 comments 0 reactions 0 assignees View on GitHub
up-for-grabs
Dominant language
C++
Stars
32.1k
Forks
6.9k
Avg merge
32m
Merged PRs (30d)
1

Description

Just like we do for point deletions in [`ComputeBottommostFilesMarkedForCompaction`](https://github.com/facebook/rocksdb/blob/4fce44fc8b8184f4800a792cf2753667e9efc9b3/db/version_set.cc#L2015-L2034), when we detect that the oldest snapshot covers all keys in a file in Lmax, and that file contains range deletions, we should mark the file as eligible for compaction.

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.