Production environment is on Azure, using Redis Cache Standard 2.5GB
.
Example 1
System.Web.HttpUnhandledException (0
My guess is that there is an issue with network stability - thus the timeouts.
Since nobody has mentioned an increase in the responseTimeout
I would play around with it. The default value is 50ms which can be easily reached. I would try it around 200ms to see if that would help with teh messages.
Taken from the configuration options:
responseTimeout={int} ResponseTimeout SyncTimeout Time (ms) to decide whether the socket is unhealthy
There are multiple issues opened on this on github. The one combining all is probably #871 The "network stability" / 2.0 / "pipelines" rollup issue
One more thing: did you try to play around with ConnectionMultiplexer.ConnectAsync()
instead ConnectionMultiplexer.Connect()
?