You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
run Redis on localhost:6379 and create a Worker with default options and no-op processing callback
Worker call brpoplpush with default rate determined by drainDelay (5 secs)
Stop redis gracefully or kill -9
The ECONNREFUSED will appear (I've also added some logging to trace each brpoplpush)
BRPOPLPUSH at 2019-10-12T09:22:26.934Z
BRPOPLPUSH at 2019-10-12T09:22:31.950Z
Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1126:14) {
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 6379
}
<the same message appears again from time to time>
Start Redis
New error messages still appears, Worker doesn't try to take new jobs from queue
UPD. I've spent some more time on debugging this. What's not good is that brpoplpush() call does not return control on such error, i.e. the promise returned neither resolves nor rejects.
The text was updated successfully, but these errors were encountered:
Yes, brpoplpush() neither resolves nor rejects as I can see.. probably there some hidden timeout so maybe it would be rejected if I'd wait more time. Need to check ioredis implementation.
Scenario
localhost:6379
and create aWorker
with default options and no-op processing callbackdrainDelay
(5 secs)kill -9
The
ECONNREFUSED
will appear (I've also added some logging to trace each brpoplpush)UPD. I've spent some more time on debugging this. What's not good is that
brpoplpush()
call does not return control on such error, i.e. the promise returned neither resolves nor rejects.The text was updated successfully, but these errors were encountered: