Keys are not distributing evenly across nodes.

[cmreddyv]

Seeing weird behaviour .. one server is at 24k keys while others are at 3 digit numbers... the key distribution is not happening properly. how to solve this and get the keys evenly distributed.

Redis Server version: 6.2.7

GoRedis client version: v7

Tried with Redis Server version: 7.0.8 and Client version v9( same behaviout)

[SoulPancake]

@cmreddyv Don't think it is related to the client.
Though If you have control over your key names, you can use hash tags to ensure a more even distribution of keys across your Redis nodes if that makes sense in your case

[cmreddyv]

@SoulPancake , not able to figure it out whether it is clientissue or server issue ... it is pushing the keys and also establishing connections to only one node in the Redis OSS server, which is making that particular server overloaded and causing time out issues.

Tried to upgrade the client to Redis V9 and server to Redis Server 7.0.8, but still the same.

func NewRedisClusterClient(config RedisConfig) *redis.ClusterClient { redisClient := redis.NewClusterClient(&redis.ClusterOptions{ Addrs: config.Hosts, Password: config.Password, DialTimeout: 10 * time.Second, // increase the timeout as needed ReadTimeout: 1 * time.Second, WriteTimeout: 1 * time.Second, PoolSize: 500, MinIdleConns: 10, PoolTimeout: 30 * time.Second, ReadOnly: true, RouteByLatency: true, })

[Odysseusailoon]

Hi it's not a client side issue, the keys' dirstribution are depending on crc16, the client just send them to the corresponding slot, you can refer to https://redis.com/blog/redis-clustering-best-practices-with-keys/

[elena-kolevska]

@cmreddyv A very common cause of this problem is the misusage of hashtags. Do you know if you're using them for naming keys? If yes, you should consider the design of the hashtag. You should include some variable part inside of the curly braces.