Repository navigation
docs: remove the Redis multi-pod migration design - #13
Merged
Merged
Conversation
The ledger engine replaced the Redis RangeCoordinator; docs/multi-pod.md described a design the code no longer has. Also drop Redis wording from the README tagline and a cursor comment.
ihaardik
approved these changes
Nov 9, 2026
RuannCarlos
approved these changes
Nov 9, 2026
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.
Summary
The ledger engine replaced the Redis
RangeCoordinatordesign, butdocs/multi-pod.mdstill documented it (Redis locks, Lua range claims,mig:ranges:*keys, async Redis→Mongo flush).docs/multi-pod.md. Multi-pod operation via chunk leases is covered in the README,docs/RUNBOOK.mdand the dashboard.src/types/cursor.ts: drop "Redis JSON" from a comment.No code behaviour change.