How to reproduce NR_CLOSED error and How to handle the NR_CLOSED error?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.6k
- Forks
- 2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 40
Description
Issue
We are using
redisnode module for Redis client to communicate with Redis server. We are facingNR_CLOSEDerror intermediately and failing to reproduce the issue. Due to failing in reproducing the issue we could not find mechanism to handle this error.
Also, the status of the
redisclient fromconnectedandreadyis not changing even after facingNR_CLOSEDerror.
Please advise how to reproduce on
NR_CLOSEDerror and how to handle in client implementation when this error occurs.
Environment
- Node.js Version:
8.0.0
- Redis Version:
3.0.2
- Platform:
Node JS
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
Start by reviewing the node-redis handling of the NR_CLOSED error and how the connected and ready client states are updated. Reproduce the behavior using Node.js 8.0.0, Redis 3.0.2, and the Node.js platform; done means documenting a reliable reproduction and the supported client-side handling.
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