StackExchange.Redis.RedisTimeoutException：超时异常响应
StackExchange.Redis.RedisTimeoutException: Timeout exception response
我们的系统使用Redis来保存一些数据。有时，根据我的应用程序的见解，我会遇到这样的超时异常：
Timeout awaiting response (outbound=0KiB, inbound=0KiB, 20640ms
elapsed, timeout is 20000ms), command=GET, active: GET
9ba45b00-52a6-41da-9acb-621665862a3b:UmsUserData, next: GET
0e730553-b6f5-4882-8c96-b853d549e385:UmsUserData, inst: 0, qu: 0, qs:
3, aw: False, rs: ComputeResult, ws: Idle, in: 1044, serverEndpoint:
Unspecified/azlink012.redis.cache.windows.net:6380, mgr: 9 of
10 available, clientName: RD0050F2931DEA, IOCP:
(Busy=1,Free=999,Min=100,Max=1000), WORKER:
(Busy=26,Free=32741,Min=100,Max=32767), v: 2.0.601.3402 (Please take a
look at this article for some common client-side issues that can cause
timeouts:
https://stackexchange.github.io/StackExchange.Redis/Timeouts)
我调查了一些参数，比如IOCP(1<100)和WORKER(26<100)，它们都是正常的。这里有什么问题？
我在 GitHub 上发现了我的问题。
if you are working with Redis, you should design your application such
that it can handle connection blips. There are number of reasons due
to which it can happen like failover, Redis patching etc.
https://github.com/StackExchange/StackExchange.Redis/issues/1378
我们的系统使用Redis来保存一些数据。有时，根据我的应用程序的见解，我会遇到这样的超时异常：
Timeout awaiting response (outbound=0KiB, inbound=0KiB, 20640ms
elapsed, timeout is 20000ms), command=GET, active: GET
9ba45b00-52a6-41da-9acb-621665862a3b:UmsUserData, next: GET
0e730553-b6f5-4882-8c96-b853d549e385:UmsUserData, inst: 0, qu: 0, qs:
3, aw: False, rs: ComputeResult, ws: Idle, in: 1044, serverEndpoint:
Unspecified/azlink012.redis.cache.windows.net:6380, mgr: 9 of
10 available, clientName: RD0050F2931DEA, IOCP:
(Busy=1,Free=999,Min=100,Max=1000), WORKER:
(Busy=26,Free=32741,Min=100,Max=32767), v: 2.0.601.3402 (Please take a
look at this article for some common client-side issues that can cause
timeouts:
https://stackexchange.github.io/StackExchange.Redis/Timeouts)
我调查了一些参数，比如IOCP(1<100)和WORKER(26<100)，它们都是正常的。这里有什么问题？
我在 GitHub 上发现了我的问题。
if you are working with Redis, you should design your application such that it can handle connection blips. There are number of reasons due to which it can happen like failover, Redis patching etc.
https://github.com/StackExchange/StackExchange.Redis/issues/1378