feat(python): expose frozen memtable metrics in memtable_stats - #8526
Merged
hamersaw merged 1 commit intoAug 14, 2026
Merged
Conversation
Surface the `frozen_count` and `frozen_bytes` fields of `MemTableStats` through the Python binding so callers can observe how much heap is still owed to flush without reaching into Rust. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
hamersaw
marked this pull request as ready for review
August 13, 2026 20:54
wkalt
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MemTableStatsalready tracksfrozen_countandfrozen_bytes, but the Python binding dropped them on the way out. This adds both keys to the dict returned byShardWriter.memtable_stats().frozen_count— frozen memtables in the read view: sealed-awaiting-flush, plus flushed ones still insidefrozen_memtable_grace.frozen_bytes— heap bytes still owed to flush. Together with the active memtable'sestimated_size_bytes, this approximates what backpressure meters againstmax_unflushed_memtable_bytes.Testing
Extends the closed-writer stats assertions in
test_mem_wal.pyto cover both keys. Not run locally — no built extension in this worktree, so CI is the first execution.🤖 Generated with Claude Code