You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am investigating a random time out that is driving me mad for days. The client is able to connect and even subscribe to channels, but then I get a random time out on a read key.
basically right after these successful operations:
Connected to GLOBAL redis 'redis-19135.c93.****:19135'.
Subscribed to redis channel 'realm-admin-dev-shared'.
on : a StringGetAsync(string key);
I get
[484]Exception App: [X]: StackExchange.Redis.RedisTimeoutException: Timeout awaiting response (outbound=0KiB, inbound=883KiB, 15942ms elapsed, timeout is 15000ms), command=GET, next: GET 6712809a829da800f1aedd2a, inst: 0, qu: 0, qs: 2, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 1718506, cur-in: 969184, serverEndpoint: redis-19135.c93.us-east-1-3.ec2.redns.redis-cloud.com:19135, mc: 1/1/0, mgr: 10 of 10 available, clientName: 958b8946-77c0-407c-bdb3-2b2bbb3d697c(SE.Redis-v2.6.80.25426), IOCP: (Busy=0,Free=800,Min=8,Max=800), WORKER: (Busy=12,Free=788,Min=8,Max=800), v: 2.6.80.25426 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
this happens randomly (not often, but too often for production).
I have investigated everything and so far I know: it's not a connection issue and it's not a load issue, because it happens only on our dev environment, with basically no users.
the only doubt is that the payload is 2MB, but they again, it times out regardless the time length (30 seconds same issue).
We are using a relatively old version of the library, so I am going to update it today to see if it makes any difference
The text was updated successfully, but these errors were encountered:
I am investigating a random time out that is driving me mad for days. The client is able to connect and even subscribe to channels, but then I get a random time out on a read key.
basically right after these successful operations:
Connected to GLOBAL redis 'redis-19135.c93.****:19135'.
Subscribed to redis channel 'realm-admin-dev-shared'.
on : a StringGetAsync(string key);
I get
[484]Exception App: [X]: StackExchange.Redis.RedisTimeoutException: Timeout awaiting response (outbound=0KiB, inbound=883KiB, 15942ms elapsed, timeout is 15000ms), command=GET, next: GET 6712809a829da800f1aedd2a, inst: 0, qu: 0, qs: 2, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 1718506, cur-in: 969184, serverEndpoint: redis-19135.c93.us-east-1-3.ec2.redns.redis-cloud.com:19135, mc: 1/1/0, mgr: 10 of 10 available, clientName: 958b8946-77c0-407c-bdb3-2b2bbb3d697c(SE.Redis-v2.6.80.25426), IOCP: (Busy=0,Free=800,Min=8,Max=800), WORKER: (Busy=12,Free=788,Min=8,Max=800), v: 2.6.80.25426 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
this happens randomly (not often, but too often for production).
I have investigated everything and so far I know: it's not a connection issue and it's not a load issue, because it happens only on our dev environment, with basically no users.
the only doubt is that the payload is 2MB, but they again, it times out regardless the time length (30 seconds same issue).
We are using a relatively old version of the library, so I am going to update it today to see if it makes any difference
The text was updated successfully, but these errors were encountered: