You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect dapr to connect to the latest version of redis.
Actual Behavior
When I connect to a redis instance deployed to kubernetes, I get the following error:
time="2022-07-25T14:55:59.411020038Z" level=fatal msg="process component statestore error: redis store: error connecting to redis at state-store-redis-cluster:6379: got 4 elements in cluster info address, expected 2 or 3" app_id=subscriber instance=subscriber-deployment-68b65fd66b-tp6tc scope=dapr.runtime type=log ver=1.7.2
Probably, it would make sense to have the redis version configurable in the component specification and then use go-redis/redis/v8 or go-redis/redis/v9 depending on what is selected there.
Thanks, would you like to create a PR that updates go.mod to the v9 version?
I'm sorry, but I currently don't have the time to do this and using redis 6 for the time being is also not an issue for us.
Expected Behavior
I expect dapr to connect to the latest version of redis.
Actual Behavior
When I connect to a redis instance deployed to kubernetes, I get the following error:
Steps to Reproduce the Problem
It seems we should use github.com/go-redis/redis/v9 to support redis 7: redis/go-redis#2085 (comment)
As you can see in the log message I am currently using dapr 1.7.2, but it seems the bug is also in the current master: https://github.com/dapr/components-contrib/blob/master/go.mod#L65
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: