-
Notifications
You must be signed in to change notification settings - Fork 913
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
fix redis broker quit very slow #443
Conversation
Codecov Report
@@ Coverage Diff @@
## master #443 +/- ##
=======================================
Coverage 47.99% 47.99%
=======================================
Files 29 29
Lines 2642 2642
=======================================
Hits 1268 1268
Misses 1234 1234
Partials 140 140
Continue to review full report at Codecov.
|
@Liv1020 : could you please add a test as well? This would help pre ent the issue from reappearing again in future. Thanks |
@charleswhchan ok, I already add test case, but i delete it after see integration-tests |
Thanks @Liv1020 . My point was that the existing tests did catch this issue before, so it would be nice to add a test a regression again in future. 😃 |
@charleswhchan Already add to integration-tests |
Thanks @Liv1020! |
@Liv1020, @RichardKnop : I tested the fix and it is working for me. |
@Liv1020 : I made a PR awhile ago and the fix is now included in v.1.6.8. Can you give it a try? |
1. When launching Redis worker and then shutdown immediately, StopConsuming() could try to close(b.StopChan) BEFORE b.StopChan is initialized inside StartConsuming(). Solution: Initialize field when object is being initialized. 2. When using Redis broker, nextTaks() usings BLPOP can block for a long time. Solution: Make timeout value configurable. See also: PR RichardKnop#406, RichardKnop#443
#439