client connection - commands do not respond
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.6k
- Forks
- 2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 40
Description
Hi.
I have a Redis server running on a machine with the descriptions below and have 5 servers on separate machines requesting to it.
After a while , say 24 hours, some of the Redis clients goes into a mode which they show connected: true in the client object but no response comes back for any command, it doesn't even throw an error , it just keeps waiting.
I'm guessing there are many factors which can cause this problem but I appreciate it if you could shine some light on this matter.
if you needed more details about the environment or something I will provide.
Environment:
- Node.js Version: 16.13.0
- Redis Server Version: v=5.0.14 sha=00000000:0 malloc=jemalloc-5.1.0 bits=64 build=20357126fbf912e0
- Node Redis Version: 3.1.2
- Platform: Debian GNU/Linux 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the stalled-command behavior with Node.js 16.13.0, Redis 5.0.14, and node-redis 3.1.2 after a long-lived connection; inspect the client connection and command handling paths. Done means the cause is identified and the client reports or handles the condition instead of waiting indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100