enhancement: reduce default WAL size for livestore#6974
Merged
zhxiaogg merged 6 commits intografana:mainfrom Apr 16, 2026
Merged
enhancement: reduce default WAL size for livestore#6974zhxiaogg merged 6 commits intografana:mainfrom
zhxiaogg merged 6 commits intografana:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reduces the default live-store WAL footprint by tuning down the default retention/cutover parameters in the live-store module configuration.
Changes:
- Reduce
complete_block_timeoutdefault from 1h to 30m. - Reduce
max_block_durationdefault from 1m to 30s. - Reduce
max_block_bytesdefault from 100MiB to 50MiB.
zhxiaogg
added a commit
to zhxiaogg/tempo
that referenced
this pull request
Apr 15, 2026
Add CHANGELOG entry for PR grafana#6974. Update configuration docs and manifest to reflect new defaults: max_block_duration 30s, max_block_bytes 50MB, complete_block_timeout 30m. Add upgrade note for Tempo 3.0.
zhxiaogg
added a commit
to zhxiaogg/tempo
that referenced
this pull request
Apr 15, 2026
Add CHANGELOG entry for PR grafana#6974. Update configuration docs and manifest to reflect new defaults: max_block_duration 30s, max_block_bytes 50MB, complete_block_timeout 30m. Add upgrade note for Tempo 3.0.
478cb0d to
b60d1be
Compare
mattdurham
reviewed
Apr 15, 2026
mattdurham
reviewed
Apr 15, 2026
mattdurham
reviewed
Apr 15, 2026
knylander-grafana
approved these changes
Apr 15, 2026
Contributor
knylander-grafana
left a comment
There was a problem hiding this comment.
Thank you for adding docs. The updates look good.
mapno
approved these changes
Apr 16, 2026
Lower default block duration (1m → 30s), max block bytes (100MB → 50MB), and complete block timeout (1h → 30m) to produce shorter, smaller WAL blocks and release completed blocks sooner.
Add CHANGELOG entry for PR grafana#6974. Update configuration docs and manifest to reflect new defaults: max_block_duration 30s, max_block_bytes 50MB, complete_block_timeout 30m. Add upgrade note for Tempo 3.0.
Correct flush_check_period default from 10s to 5s in config reference. Update upgrade guide to avoid misleading max_block_duration row that showed 1m when the current default is now 30s.
Combine the two separate upgrade sections into one table, use MiB instead of MB, remove PR links, and show full default changes from the original values.
…after to 15m Lower complete_block_timeout from 30m to 20m so completed blocks are released sooner. Align metrics query_backend_after with the search default (both now 15m). Update all docs accordingly.
c63d19c to
2dc8ea4
Compare
zalegrala
approved these changes
Apr 16, 2026
Contributor
zalegrala
left a comment
There was a problem hiding this comment.
Looks reasonable to me. It might be worth including a bit more about the reason to change the default in the PR summary.
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.
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]