Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mention ASK and TRYAGAIN for replicas in READONLY command manual #142

Merged
merged 2 commits into from
Jun 2, 2024
Merged

Mention ASK and TRYAGAIN for replicas in READONLY command manual #142

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4cd52e0
Mention ASK and TRYAGAIN for replicas in READONLY command manual
zuiderkwast Jun 1, 2024
5ecebb5
Mention version
zuiderkwast Jun 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions commands/readonly.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,6 @@ master node. This may happen because:

1. The client sent a command about hash slots never served by the master of this replica.
2. The cluster was reconfigured (for example resharded) and the replica is no longer able to serve commands for a given hash slot.
3. Since Valkey 8.0, if a slot migration is ongoing.
In this case the replica can return an ASK redirect or a TRYAGAIN error reply.
In earlier versions, replicas are not aware of ongoing slot migrations.