Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark auto-expired key-value pairs in the mutable log as tombstoned #1114

Open
badrishc opened this issue Mar 20, 2025 · 0 comments
Open

Mark auto-expired key-value pairs in the mutable log as tombstoned #1114

badrishc opened this issue Mar 20, 2025 · 0 comments

Comments

@badrishc
Copy link
Collaborator

badrishc commented Mar 20, 2025

Feature request type

enhancement

Is your feature request related to a problem? Please describe

When an expiration time is attached to entries in the store, after expiration, they are not removed from the log until (and if) they tier down to storage and get compacted.

We would like to add some way to tombstone these records so that (1) the heap objects are freed in case of the object store; and (2) the log space can be reused for new objects using revivification, in case of the main store.

Describe the solution you'd like

One way to accomplish this is to have a periodic background scanner thread that scans (only the mutable region of) the log, and tombstones any expired entries.

Describe alternatives you've considered

No response

Additional context

See #1097 for a more detailed discussion of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant