broker: limit concurrent primary fragment persists#460
Merged
williamhbaker merged 1 commit intomasterfrom Feb 18, 2026
Merged
Conversation
Add a semaphore to Persister that bounds concurrent primary persist goroutines. When many journals share an epoch-aligned flush_interval, they all roll their fragments simultaneously, spawning a potentially large number of concurrent cloud uploads which may allocate significant per-upload buffers and cause memory issues. This semaphore will prevent unbounded memory growth when persisting many journals. Co-Authored-By: Claude Opus 4.6 <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
2 participants
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.
Add a semaphore to Persister that bounds concurrent primary persist goroutines.
When many journals share an epoch-aligned flush_interval, they all roll their fragments simultaneously, spawning a potentially large number of concurrent cloud uploads which may allocate significant per-upload buffers and cause memory issues.
This semaphore will prevent unbounded memory growth when persisting many journals.