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
Currently, the queue.close() takes almost 0.5s to close, because close() eventually calls waitForJob which delay() for 100ms currently (and that's being multiplied, eventually .close() becoming 0.5s slow).
Anyway, if close() has been called, can we detect this scenario and then avoid calling delay() in that case? Or maybe some better solution.. 🤔
In the catch block, the error is: Error: Connection is closed (I just added the log to see it).
Two weeks back I faced a similar issue with the bull library. However, now I've switched to bullmq. Lots of the implementation I see is very similar. So maybe the other thread would be helpful as well, so here it is: OptimalBits/bull#2372
The text was updated successfully, but these errors were encountered:
Currently, the
queue.close()
takes almost0.5s
to close, becauseclose()
eventually callswaitForJob
whichdelay()
for100ms
currently (and that's being multiplied, eventually.close()
becoming0.5s
slow).Anyway, if
close()
has been called, can we detect this scenario and then avoid callingdelay()
in that case? Or maybe some better solution.. 🤔bullmq/src/classes/worker.ts
Lines 467 to 472 in 5b1a71a
In the
catch
block, the error is:Error: Connection is closed
(I just added the log to see it).Two weeks back I faced a similar issue with the
bull
library. However, now I've switched tobullmq
. Lots of the implementation I see is very similar. So maybe the other thread would be helpful as well, so here it is: OptimalBits/bull#2372The text was updated successfully, but these errors were encountered: