node-redis icon indicating copy to clipboard operation
node-redis copied to clipboard

How to reproduce NR_CLOSED error and How to handle the NR_CLOSED error?

Open prashanthmadduri opened this issue 4 years ago • 3 comments

Issue

We are using redis node module for Redis client to communicate with Redis server. We are facing NR_CLOSED error 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 redis client from connected and ready is not changing even after facing NR_CLOSED error.

Please advise how to reproduce on NR_CLOSED error 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

prashanthmadduri avatar Mar 24 '20 14:03 prashanthmadduri

Has this issue resolved? I am still facing the same issue.

aadi99999 avatar Nov 08 '20 17:11 aadi99999

Also having same issue. Bouncing service seems to fix it, but redis ping comes back fine, so my health check is giving a false positive.

Bellk17 avatar Dec 01 '20 22:12 Bellk17

Did anyone figure this out? We're having the same issue. It's intermittent and started happening in the last 6 months or so

richtu4n avatar Jul 23 '22 13:07 richtu4n