Repository navigation
RS: restore featureset instructions - #4221
Merged
Merged
Conversation
Contributor
Contributor
Contributor
Contributor
Author
|
Approved by Git Shmueli via slack |
EliShteinman
added a commit
to EliShteinman/docs
that referenced
this pull request
Oct 8, 2026
Restores the Active-Active feature set version guidelines and upgrade steps to upgrade-active-active.md. Co-Authored-By: Claude Opus 5.5 <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
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.
Note
Low Risk
Documentation-only changes to Active-Active upgrade procedures; no application or infrastructure code is modified.
Overview
Restores and expands Active-Active feature set version guidance in the upgrade doc.
Under Feature set version guidelines, it now notes that feature set versioning starts in Redis Software 5.6.0 and adds explicit upgrade rules: feature set version 0 is deprecated from 6.0.20 onward, and databases should be on the latest feature set version before moving to 6.0.20+ to avoid failed upgrades.
A new Upgrade feature set version section walks operators through fixing an
OLD CRDB FEATURESET VERSIONstatus—complete the normal database upgrade (with current protocol version), resolve the<CRDB-GUID>viacrdb-cli crdb list, then runcrdb-cli crdb update --crdb-guid <CRDB-GUID> --featureset-version yes.Reviewed by Cursor Bugbot for commit 3816cf2. Bugbot is set up for automated code reviews on this repo. Configure here.