Open IgorKuznetsov93 opened 3 years ago
Hi @IgorKuznetsov93,
I got the same issue with you, how did you fix it? My ioredis version is 4.27.4
Thanks a lot
Hi @IgorKuznetsov93,
I got the same issue with you, how did you fix it? My ioredis version is 4.27.4
Thanks a lot
Hi! I thought I had solved the problem, but no, my logger just broke. Unfortunately, the problem still remains Reopen issue
Getting the same issue on the same ioredis version. Any update?
I have the same issue Please fix it
IORedis Version: 4.28.5 Error Line: node_modules\ioredis\built\redis\index.js:327:37
l have same problem
Hi Has anyone fixed this issue yet ? @zry754331875
We're also seeing this issue, quite a few years have gone by now. Any plans on fixing it? We're using version 5.3.0
.
The error is expected if all your sentinels were not available at that time. More information are helpful for us to debug it further if that's not your case.
Our applications have the same problem every 40 min, when we get that kind of error. We are using the Bitnami helm chart with a 3 node setup of REDIS/sentinel. And all sentinels are online and reachable via an internal google loadbalancer service.. If you need more info please let us now. Is there some kind of tasks that run every 40 min or a connection reset or something else? Thanks in advice.
Our application is not even able to establish the connection the very first time, Setup is pretty simple I am just testing in my local system and I have only one sentinel and one redis instance (both are running on docker
ioredis:redis status[127.0.0.1:26379]: wait -> connecting
ioredis:redis queue command[127.0.0.1:26379]: 0 -> sentinel([ 'get-master-addr-by-name', 'redis-queue' ])
ioredis:redis status[127.0.0.1:26379]: connecting -> connect
ioredis:redis status[127.0.0.1:26379]: connect -> ready
ioredis:connection send 1 commands in offline queue
ioredis:redis write command[127.0.0.1:26379]: 0 -> sentinel([ 'get-master-addr-by-name', 'redis-queue' ])
ioredis:redis write command[127.0.0.1:26379]: 0 -> sentinel([ 'sentinels', 'redis-queue' ])
ioredis:SentinelConnector Updated internal sentinels: [{"host":"127.0.0.1","port":26379}] @1
ioredis:SentinelConnector resolved: 192.168.80.2:6379 from sentinel 127.0.0.1:26379
ioredis:redis status[127.0.0.1:26379]: ready -> close
ioredis:connection skip reconnecting since the connection is manually closed.
ioredis:redis status[127.0.0.1:26379]: close -> end
ioredis:connection error: Error: connect ETIMEDOUT
at Socket. ioredis/built/Redis.js:170:41)
at Object.onceWrapper (node:events:627:28)
at Socket.emit (node:events:513:28)
at Socket._onTimeout (node:net:565:8)
at listOnTimeout (node:internal/timers:564:17)
at processTimers (node:internal/timers:507:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect'
}
redis connection error!: Error: connect ETIMEDOUT
at Socket. (
node_modules/ioredis/built/Redis.js:170:41)
at Object.onceWrapper (node:events:627:28)
at Socket.emit (node:events:513:28)
at Socket._onTimeout (node:net:565:8)
at listOnTimeout (node:internal/timers:564:17)
at processTimers (node:internal/timers:507:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect'
}
I also observe random timeouts towards redis, with a mix of "All sentinels are unreachable" and generic timeout errors being printed. The sentinels appear to be completely healthy.
The application performs around 1-2k queries per second and the timing of the error event seems completely random, but there are usually around 500-1000 such errors per day:
I have currently disabled retries via maxRetriesPerRequest: null
, but will check if enabling retries will get rid of the errors. Other options I tried are enabling enableAutoPipelining
but it had no effect.
Problem still exists...
Problem still exists. Time to find a good redis client. This issue exists since 6 years. Ioredis team failed to fix this issue.
Hello. Can you help me with this issue? This already spammed my logs My connect options:
Version: "ioredis": "4.27.6", Logs: