This repository was archived by the owner on Oct 22, 2019. It is now read-only.
Fix errant keys in Redis scripts #111
Open
Conversation
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
The metric labels and command types were inappropriately specified as KEYS in the Redis scripts. This meant there was no way to avoid a `CROSSSLOT Keys in request don't hash to the same slot` error when using a Redis cluster that hashes keys to select a specific node.
Author
|
Resolves: #110 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
The metric labels and command types were inappropriately specified as
KEYS in the Redis scripts. This meant there was no way to avoid a
CROSSSLOT Keys in request don't hash to the same sloterror when usinga Redis cluster that hashes keys to select a specific node.