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

[prashanthmadduri]

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

[aadi99999]

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

[Bellk17]

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.

[richtu4n]

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