-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Connection hangs forever using lettuce and timeouts are not working #2863
Comments
Please attach a thread dump for further diagnosis. |
Thanks for the quick response! :) |
the offending thread has this trace:
Some open telemetry instrumentation blocks the event loop thread so it is out of scope of the driver and out of scope of Spring Data. Generally, there's some proper tracing support via Micrometer Tracing that doesn't require instrumentation by a Java agent. |
thanks for your help, ill take a look |
FYI: disabling the redis implementation of the otel client via OTEL_INSTRUMENTATION_LETTUCE_ENABLED: 'false' worked fine. We didnt had this issue anymore. Thank you for your help :) |
Hi,
we use spring-boot-starter-data-redis:3.2.2 with a single redis instance and configured these timeouts:
But we still notice that sometimes, after the application ran for a day, that the redis connection just completely dies and any call using @Cacheable annotation just hangs forever.
Looking into making the connection more reliable via this thread here: redis/lettuce#1428
But iam also wondering why these three timeouts are not working and the connection still hangs forever. Any other call works fine and after a restart the application is working again.
The text was updated successfully, but these errors were encountered: