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.
general way of catching connection related lettuce redis exceptions
See original GitHub issueHi. I am trying to implement my own custom reconnection logic handling such that whenever there are any exceptions throwing related to connection problem it will trigger this custom reconnection logic to create a new lettuce client (through Load Balancer). Is there a general way to catch all connection related exceptions? I have seen many connection problem that are instanceof RedisException (which is very general). Can you offer any tips?
I am currently using lettuce connection pooling as my client
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 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
For that case, please configure a custom
SocketAddressResolver. DNS resolvers might not be used when using e.g. domain sockets.Hi @mp911de so do you think that I can customize the autoreconnect behavior such that whenever connect or reconnect is triggered it will invoke the custom connect logic with
DefaultClientResources.builder().dnsResolver(host -> custom_reconnect_logic(host))? Cuz for autoreconnect I don’t want it to just try reconnect to the same server node that was configured in redis uri initially, but to a different server node [through load balancer to find the next available server node to connect to] (the custom reconnect logic)