Conversation
…uto Tiering docs
Contributor
Contributor
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
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
2 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.
Note
Low Risk
Markdown-only documentation changes with no product code or configuration behavior changes.
Overview
Documentation-only updates across Redis Enterprise Auto Tiering (7.4, 7.8, 7.22), versioned quickstarts, and the shared Flex / Auto Tiering (
databases/flash) pages.Anti-patterns and sizing: The “not recommended” guidance is expanded and normalized to bullet lists. It now calls out high key count and long key names (all key names stay in RAM), large collections (hashes/sets/lists that cannot be partially tiered to flash), and keeps existing warnings on broad access, large working sets, and churn. The combined flash overview applies the same anti-patterns to both Flex and Auto Tiering (wording was Flex-only in places).
OOM with free flash: After the existing 4GB flash limit discussion, docs add that oversized or RAM-only keys can still cause shard OOM when RAM is exhausted, even if flash has capacity. 7.4 and 7.8 Auto Tiering overviews gain the full Size limits for keys and values section (previously missing vs 7.22).
Quick starts: New Before deployment sections on all affected quickstarts summarize these checks before install/cluster setup.
Reviewed by Cursor Bugbot for commit dda8259. Bugbot is set up for automated code reviews on this repo. Configure here.