azure cache for Redis: The message timed out in the backlog attempting to send because no connection became available

Question

need help. i just started using azure ache for redis and i am getting these exceptions, not sure what to fix based on this message. i created 2 cache instances one with public access and other with private access.

code in program.cs:

services.AddStackExchangeRedisCache(action =>

{

action.InstanceName = redisCacheOptions.InstanceName;

action.Configuration = redisCacheOptions.Configuration;

action.ConfigurationOptions = redisCacheOptions.ConfigurationOptions;

action.ConfigurationOptions.EndPoints.Add("XXXX.redis.cache.windows.net", 6380);  // with out this line it is giving no end point found exception. 

});

DI :

public CacheHelper(IDistributedCache distributedCache, ILogger<CacheHelper> logger)

{

 _distributedCache = distributedCache;

 _logger = logger;

}

call to get cache key value:

await _distributedCache.GetStringAsync(key, token);

private network:

'The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=HMGET, timeout: 5000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 1, serverEndpoint: XXXXX.redis.cache.windows.net:6380, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: NARESH(SE.Redis-v2.7.27.49176), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=0,Free=32767,Min=20,Max=32767), POOL: (Threads=9,QueuedItems=0,CompletedItems=458,Timers=12), v: 2.7.27.49176 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)'

public:

: 'The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: UnableToConnect (None, 0-read, last-recv: 0) on XXXX.redis.cache.windows.net:6380/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 5s ago, last-write: 4s ago, unanswered-write: 4s ago, keep-alive: 60s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.7.27.49176, command=HMGET, timeout: 5000, inst: 0, qu: 0, qs: 12, aw: False, bw: CheckingForTimeout, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 1, serverEndpoint: XXXX.redis.cache.windows.net:6380, conn-sec: 4.99, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: NARESH(SE.Redis-v2.7.27.49176), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=0,Free=32767,Min=20,Max=32767), POOL:

Answer 1

thank you for reply. its finally narrow downed to DNS resolver. my IT admin did added the DNS entry and it resolved.