![]() ![]() ReconnectRetryPolicy = new LinearRetry(5000),ĮndPoints = , Azure's metrics show that the number of connected clients remains stable, even though the number of affected machines is high enough that we'd expect to see it if there were issues.Īll of these facts that came out of our investigation leads us to believe this may be a bug in the library, even though our initial guess was that it'd be the network.ĬonfigurationOptions sentinelconfiguration = new().no upgrades, no cluster size changes, or anything like that). There are no ongoing maintenance operations whatsoever from Azure Cache for Redis at the times this happens (i.e.No errors are shown at the time these exceptions are thrown. Connection strings do include ssl, and we have the Redis.StackExchange's internal logs, which show we are connecting with Tls1.2, as expected. The Redis instances are Azure Cache for Redis.We don't seem to have any issues in this area (this is also inside a datacenter, so network is relatively stable). We have looked into network connectivity and have performed packet captures. ![]() ![]() ![]() Restarting the process seems to work at least temporarily, but is not really a long-term option for us.This doesn't work, the errors come back again. We have tried re-creating the ConnectionMultiplexer after a certain amount of exceptions.End of stack trace from previous location where exception was thrown -Īt .Throw()Īt .HandleNonSuccessAndDebuggerNotification(Task task)Īt ._0.MoveNext()Īt ._Displa圜lass22_0.b_0>d.MoveNext() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |