Sentinel preferredSlaves option #370
Merged
Conversation
This file contains 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
local reads in a distributed environment. Value can be an array of objects with required properties “ip” and “port” and option property of “prio” indicating the priority, defaults to 1, lower numbers preferred first. If the value is a function the available slaves are passed into it, expecting a single slave as the response. If no preferred slave is found a random one is returned from those available. Updated tests to return bad values in SENTINEL slaves command but still select the correct one based on the preferredSlave result.
|
Released with 2.4.0. Thank you for the pull request (and the documentation for the changes) :-) |
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.
Option to specify a preferred slave (or slaves by priority) when connecting to a Sentinel group.
Fixes #38 .