Add meta_compact_size option to further control JetStream meta group compaction/snapshotting#7521
Merged
neilalexander merged 1 commit intomainfrom Nov 6, 2025
Merged
Conversation
…p compaction/snapshotting Signed-off-by: Neil Twigg <neil@nats.io>
Member
|
I still think we should prefer to never compact under normal situations and only on restart. |
This was referenced Nov 7, 2025
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
4 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.
This continues from #7484 by adding
meta_compact_sizetoo, which allows controlling the upper limit of the metalayer log before compaction by size rather than the number of entries.If both
meta_compactandmeta_compact_sizeare configured, compaction happens when the lower of the two is reached.If neither are configured, each
doSnapshot()call will compact, as before.Signed-off-by: Neil Twigg neil@nats.io