i’m not sure if its ok to revive this topic or create a new one.
We actually have the same issue with azure redis-> we run into the exact same Exception as grahamlaidler describes.
So i’m thinking of adjusting the values for
RedisConfig.DefaultRetryTimeout = 3000;
RedisConfig.BackOffMultiplier = 10;```
to fight the sympton with a retry. Do you have some experiences/recommendations for those values for azure redis?
thank you for any tips/hints.
In case others are experiencing a similar problem with occassional connection drop to Azure Redis, we have found a workaround that works in our case which was to disable SSL in the connection string.
Error was: »An existing connection was forcibly closed by the remote host«
***@subdomain.redis.cache.windows.net?ssl=true => ***@subdomain.redis.cache.windows.net:6379?ssl=false
This workaround followed the solution mythz provided in version 4.0.55, where the connection drop due to NOAUTH was handled with auto-reconnect. So we had a way to reconnect but still had to figure out why it happens. The original thread is here