-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Utilizing redis WAIT functionality #344
Comments
I suppose it would be. Were you having an issue with consistency across your replicas? |
Yeah we're noticing request coming in with expired session data. Even up to 15 seconds after we have updated that specific session. Our redis cluster consists of 4 nodes each with 1 replica. It almost seems like the session write didn't succeed from the previous request but were not seeing anything in our logs. This is happening ~70 times a day. Is there a flag I need to set to get more logging info? |
Well if anything i'd want this to be included in DistributedStore, since that's the class that handles distributed deployments of redis, and i think it handles clusters as well. There aren't any flags you can set in |
@Hatched-Kyle are you potentially having the same issue as redis-store/redis-rack#70? |
Is is possible to utilize the redis WAIT command to help guarantee strong consistency across all nodes?
https://redis.io/commands/wait
The text was updated successfully, but these errors were encountered: