Closed
Description
Hi there, I use go-redis to connect to our Elasticache cluster of 10 shards and we noticed that our keys are hashes to slots in a way that we end up hammering the primary of the same 2 shards while the other shards and their nodes remain largely idle. To rebalance our traffic and spread the keys better we were considering to switch to a consistent hashing approach, but it looks like the Ring implementation of go-redis does not accept a ClusterClient, but just a regular Client with the shard lists and I don't understand why is that? Am I missing something?
Metadata
Metadata
Assignees
Labels
No labels