Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Connection Leak in Cluster Topology Refresh
See original GitHub issueWe are using Lettuce 5.0.2 to connect to a Redis cluster (Elasticache and Azure) with SSL enabled. We notice that once we enable periodic topology refresh the number of open connections to the cluster steadily increases.
We can reproduce the issue with a simple and pure Lettuce application which does nothing but periodic topology refreshes. The issue is also reproducible with SSL disabled.
The root cause of the issue seems to lie in the io.lettuce.core.cluster.topology.Connections#drainConnections method which mixes a local variable and an instance variable in an unintended way.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s fixed now in snapshot builds of Lettuce 5.0.3 and 5.1.0.
The most recent version is 5.2.1. Can you retest and file a ticket if the problem persists?