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
Failed to submit a listener notification task. Event loop shut down? #5795
Comments
We get the same issue on 3.29.0 From what I understand it comes from tasks being completed after EventExecutor shutdown and not being able to register execution completed events to their listeners. When looking into it I found that there is a Further I found that the
redisson/redisson/src/main/java/org/redisson/connection/MasterSlaveConnectionManager.java Line 515 in e3a851a
My guess is that the intended code is timeoutInNanos = Math.max(0, timeoutInNanos - (System.nanoTime() - startTime)); Instead of subtracting 2 times the current system nano time from the With redisson/redisson/src/main/java/org/redisson/connection/MasterSlaveConnectionManager.java Line 547 in e3a851a
Something like this could be added to RedissonTest if my understanding is correct that this is broken. (The test fails on current master but succeeds with the change proposed above) @Test
public void testShutdownQuietPeriod() {
long quietPeriod = TimeUnit.SECONDS.toMillis(1);
long timeOut = quietPeriod + TimeUnit.SECONDS.toMillis(1);
RedissonClient r = createInstance();
long startTime = System.currentTimeMillis();
r.shutdown(quietPeriod, timeOut, TimeUnit.MILLISECONDS);
long shutdownTime = System.currentTimeMillis() - startTime;
Assertions.assertTrue(shutdownTime > quietPeriod);
} (If I would have known how to and/or would have had the appropriate access, I would have opened a PR with the suggested change) |
Thanks for pointing out. It's a bug. You can follow the instruction described in this article for creating a PR https://opensource.com/article/19/7/create-pull-request-github |
Merged |
Expected behavior
Should not occur
Actual behavior
Occurred
stack trace
Steps to reproduce or test case
Sorry, I don't know well.
Redis version
Elasticache Redis 7.1.0
Redisson version
3.28.0
Redisson configuration
The text was updated successfully, but these errors were encountered: