StackExchange / StackExchange/StackExchange.Redis

SocketFailure on xx.redis.cache.windows.net:6380/Interactive, Idle/Faulted, last: GET, origin: ReadFromPipe, outstanding: 12, last-read: 22s ago

Open
#2,703 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

☁️ platform:Azure
Dominant language
C#
Stars
6.2k
Forks
1.6k
Avg merge
1d 15h
Merged PRs (30d)
43

Description

Client library: "StackExchange.Redis" Version="2.7.33"
Redis: Azure cache for Redis
Symptom:
SocketFailure on xx.redis.cache.windows.net:6380/Interactive, Idle/Faulted, last: GET, origin: ReadFromPipe, outstanding: 12, last-read: 22s ago, last-write: 1s ago, unanswered-write: 19s ago, keep-alive: 60s, state: ConnectedEstablished, mgr: 9 of 10 available, in: 0, last-heartbeat: 1s ago, last-mbeat: 0s ago, global: 0s ago, v: 2.7.33.41805 Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

This issue happens rarely and intermittently. from the https://github.com/StackExchange/StackExchange.Redis/issues/1100, it should be fixed 2.1.x. but the latest version is used and the issue still happen.

Any help would be greatly appreciated.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the reported StackExchange.Redis 2.7.33 diagnostics and compare them with issue #1100, focusing on the Azure Cache for Redis connection on port 6380. Reproduce the intermittent SocketFailure and establish a reliable failure condition and regression test or documented resolution; the report does not name a source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, redis
Domain
backend, cloud, databases
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.