-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Worker reconnection after explicit .close() call due to Redis worker reconnection #2552
Closed
1 task done
Labels
bug
Something isn't working
Comments
I am seeing a potential issue actually, clearTimeout is not being called if the call to bzpopmin throws an exception. Fix incoming... |
@ScreaminSauce do you mind testing with version 5.7.8 to see if the issue is resolved? |
New version ran successfully - test output with ioredis logs below:
Cheers for the quick turnaround on this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v5.7.7
Platform
NodeJS
What happened?
Using the current release, it appears that Worker reconnection logic keeps the ioredis client open (and reconnects) after the .close() method has been called on both the Queue and the Worker
v5.7.6 does not hang after test completion, leading me to believe the cause may be the updated ioredis client including PR #2543 (#2543)
How to reproduce.
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: