ConnectionTimeoutError

[DhiegoHenriqueA]

Description

I was using version 2.8.0 of redis in an aws lambda with node in version 14.x, when updating redis version to 4.6.7 and node to version 18.x I started getting timeouts in just a few moments.

Redis Client Error ConnectionTimeoutError: Connection timeout
at Socket. (/opt/nodejs/node_modules/@redis/client/dist/lib/client/socket.js:178:124)
at Object.onceWrapper (node:events:627:28)
at Socket.emit (node:events:513:28)
at Socket._onTimeout (node:net:570:8)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7)

this is my code:
const redis = require('redis')
const client = redis.createClient({
url: redis://${process.env.REDIS_IP}:${process.env.REDIS_PORT},
pingInterval: 2000,
socket: {
connectTimeout: 7000
}
})
client.connect()

client.on('error', err => console.log('Redis Client Error', err))

Node.js Version

18.17.0

Redis Server Version

6.2.6

Node Redis Version

4.6.7

Platform

No response

Logs

Redis Client Error ConnectionTimeoutError: Connection timeout
    at Socket.<anonymous> (/opt/nodejs/node_modules/@redis/client/dist/lib/client/socket.js:178:124)
    at Object.onceWrapper (node:events:627:28)
    at Socket.emit (node:events:513:28)
    at Socket._onTimeout (node:net:570:8)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)

[pedrokaroth]

I have the same issue here, any update to this?

[juniorSchulzDev]

I have the same issue here, any update to this?

[tchiteu]

Same issue here...

[leibale]

Hi everyone,

Debugging a "timeout issue" can be quite challenging as it is often triggered by another underlying error. For instance, if the Redis server event loop gets blocked (which can be simulated using DEBUG SLEEP 10000 – DO NOT run this on your production server), any client attempting to open a socket will experience a timeout. Similarly, if the Node.js event loop gets blocked, timeouts will occur as well (see here for an example). Additionally, it's important to consider the possibility of an actual network issue causing the problem. Lastly, there could be an undiscovered bug in the package; however, I must mention that I personally (and many other users) run servers with the same package version and haven't experienced any timeouts.

If anyone has any insights, please feel free to share them..

Duplicate of #1656