Open JoHuang opened 2 years ago
Hi, the same error can happen when calling quit()
on closed connection, e.g. due to termination from the redis server side. Would you please expose the connection status on redis client instance so we could conditionally call quit? Right now the workaround is to listen on close/end
and other events to tract the connection status.
When connecting to Redis via TLS connection, calling quit() causes an unhandled error. No issue for non-TLS mode.
node.js : v16.15.0 ioredis version: 4.28.5, 4.28.0 tested with Redis.com and DigitalOcean managed Redis
debug message:
non-TLS normal case: