Hi, I am getting sporadic errors when using Azure Redis & ServiceStack.Redis. I have read that during large “fork” operations Redis can be offline for some time.
Is there anything I can do to handle this intelligently?
G
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host; at ServiceStack.Redis.RedisNativeClient.FlushSendBuffer()"
hi demis,
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.
tobi
this looks very promising! do you already know when v4.0.56 is officallyout? pre releases affect our build chain so maybe we don’t have to adapt there if v4.0.56 is just about to be released.
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«
Workaround:
***@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