Fix archive compaction OOM on large parquet groups#792
Merged
erikdarlingdata merged 1 commit intodevfrom Apr 6, 2026
Merged
Conversation
DuckDB was running out of memory compacting monthly parquet files (e.g., 4 query_snapshots files needing ~480MB to merge). Three changes: - Raise DuckDB memory cap from 2GB to 4GB - Create a fresh DuckDB connection per (month, table) group so memory is fully released between groups - For groups with >2 files, merge incrementally in pairs (smallest-first) instead of all at once, reducing peak memory significantly Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Fixes recurring hourly OOM:
Failed to compact 202603/query_snapshots (4 files) — Out of Memory Error: failed to allocate data of size 480.0 MiBTest plan
🤖 Generated with Claude Code