DOC-14: document Cloud topic segment size default#626
Open
micheleRP wants to merge 2 commits into
Open
Conversation
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a “Segment size” row to the topic properties table. The documentation describes the log segment maximum size, Redpanda’s behavior when the limit is reached, the 128 MiB cluster-level default, and per-topic overrides through Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Add a Segment size row to the Cloud topic-properties table. Redpanda Cloud sets log_segment_size to 128 MiB at the cluster level, unlike self-managed Redpanda (1 GiB), and this was not documented anywhere in cloud-docs. The per-tier min/max are intentionally described as tier-dependent rather than hardcoded, pending Cloud-team confirmation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
73f7e50 to
1e39014
Compare
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.
Resolves DOC-14.
What
Adds a Segment size row to the topic-properties table on the Cloud "Topics Overview" page (
modules/develop/pages/topics/create-topic.adoc).Why
Redpanda Cloud sets
log_segment_sizeto 128 MiB at the cluster level, unlike self-managed Redpanda (1 GiB). This Cloud-specific default was not documented anywhere in cloud-docs, so Cloud users relying on the self-managed default were misinformed. Verified against cloudv2main(install-pack fixtures, cluster-config runbook).Note for reviewers
The per-tier min/max are intentionally described as "limits that depend on your cluster tier" rather than hardcoded.
install-pack/generate-tiers.py(max = tier default) and the install-pack fixtures (max 256 MiB, min 16 MiB) disagree, so the exact range isn't reliable across tiers. Recommend confirming the min/max with the Cloud team before stating explicit numbers.Preview pages
🤖 Generated with Claude Code