-
Notifications
You must be signed in to change notification settings - Fork 259
Add resharding section to memory-limit documentation #2146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Add comprehensive resharding process overview explaining 3-stage process - Document performance characteristics and factors affecting resharding duration - Include flex sharding performance improvements and key length considerations - Add traffic impact analysis during resharding operations - Use proper Hugo note shortcode for atomic operation warning - Align content with Google technical writing style for clarity and consistency This addition provides Redis Enterprise administrators with essential information for planning resharding operations and understanding performance implications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few comments with my initial thoughts.
content/operate/rs/databases/memory-performance/memory-limit.md
Outdated
Show resolved
Hide resolved
content/operate/rs/databases/memory-performance/memory-limit.md
Outdated
Show resolved
Hide resolved
content/operate/rs/databases/memory-performance/memory-limit.md
Outdated
Show resolved
Hide resolved
content/operate/rs/databases/memory-performance/memory-limit.md
Outdated
Show resolved
Hide resolved
- Refine content based on review feedback - Improve clarity and technical accuracy of resharding documentation - Update performance characteristics and factor descriptions - Enhance readability and flow of the resharding process explanation
…lex sharding' - Standardize terminology throughout the resharding performance section - Ensure consistent naming convention for flexible sharding feature
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mich-elle-luna a few comments:
- flexible sharding is not supported (yet) in Redis SW. Support will be added only next year (CY2026) - no ETA yet. Thus, this PR should not be published until further notice.
- When we do release it in RS, we will not be using the term "flexible shards", which is an internal term, not a customer-facing term.
Hi @yoavredis thank you, much appreciated! I removed the references to resharding based on your comment in the ticket if you want to re-review. |
Adds information about resharding duration