RS: clarify reserved_ports also applies to internal shard traffic - #3810
Open
tannersherman-redis wants to merge 2 commits into
Open
RS: clarify reserved_ports also applies to internal shard traffic#3810tannersherman-redis wants to merge 2 commits into
tannersherman-redis wants to merge 2 commits into
Conversation
Update the reserved_ports documentation to make clear that the setting prevents the cluster from assigning ports to internal shard traffic in addition to database endpoints. Adds 20048 to the examples in the rladmin cluster config command and the rladmin/REST API reference tables
Contributor
Contributor
🧠 Redis MemoryFound 7 related items from repository history (2 new this commit):
Memory updated at 4d7f716 |
kaitlynmichael
changed the title
kaitlynmichael
requested changes
Aug 13, 2026
kaitlynmichael
left a comment
kaitlynmichael
left a comment
Contributor
There was a problem hiding this comment.
Just some wording suggestions for clarity
…range behavior with reserved_ports and updated language for better clarity out of review
|
|
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.
Update the reserved_ports documentation to make clear that the setting prevents the cluster from assigning ports to internal shard traffic in addition to database endpoints. Adds
20048to the examples in the rladmin cluster config command and the rladmin/REST API reference tables.Note
Low Risk
Markdown-only reference updates with no product or runtime changes.
Overview
Documentation-only updates across RS networking and reference pages (versions 7.4, 7.8, 7.22, 8.0, and the main
operate/rstree).Clarifies that
reserved_portsblocks the cluster from using listed ports/ranges for database endpoints and internal shard traffic, not just endpoints. A new note after the port table states that 20000–29999 is fixed for shard traffic and thatreserved_portscan still exclude specific ports or ranges inside that band from assignment.Reserve ports prose,
rladmin cluster configparameter text, and the REST cluster object field description are aligned with that behavior. Examples now include20048alongside existing samples to show reserving a port in the shard range.Reviewed by Cursor Bugbot for commit 4d7f716. Bugbot is set up for automated code reviews on this repo. Configure here.