Stuck on an issue?
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.
why lettuce client keep reconnecting
See original GitHub issueWe’re using connection pooling with maxTotal set to 30. I found in the logs the are lots of reconnection events happened and would like to know why the client keep reconnecting to our redis cluster.
Logs:
2018-09-20 10:46:57,103 [lettuce-eventExecutorLoop-4-7] INFO - Reconnecting, last destination was /192.168.10.89:7004
2018-09-20 10:46:57,103 [lettuce-eventExecutorLoop-4-6] INFO - Reconnecting, last destination was /192.168.10.89:7000
2018-09-20 10:46:57,103 [lettuce-eventExecutorLoop-4-5] INFO - Reconnecting, last destination was /192.168.10.89:7000
2018-09-20 10:46:57,103 [lettuce-nioEventLoop-6-14] INFO - Reconnected to 192.168.10.89:7000
2018-09-20 10:46:57,103 [lettuce-nioEventLoop-6-13] INFO - Reconnected to 192.168.10.89:7004
2018-09-20 10:46:57,103 [lettuce-nioEventLoop-6-15] INFO - Reconnected to 192.168.10.89:7000
2018-09-20 10:46:57,203 [lettuce-eventExecutorLoop-4-8] INFO - Reconnecting, last destination was /192.168.10.11:7000
2018-09-20 10:46:57,203 [lettuce-eventExecutorLoop-4-13] INFO - Reconnecting, last destination was /192.168.10.159:7003
2018-09-20 10:46:57,203 [lettuce-eventExecutorLoop-4-12] INFO - Reconnecting, last destination was /192.168.10.159:7000
2018-09-20 10:46:57,203 [lettuce-eventExecutorLoop-4-11] INFO - Reconnecting, last destination was /192.168.10.203:7005
2018-09-20 10:46:57,203 [lettuce-eventExecutorLoop-4-9] INFO - Reconnecting, last destination was /192.168.10.203:7004
2018-09-20 10:46:57,203 [lettuce-eventExecutorLoop-4-10] INFO - Reconnecting, last destination was /192.168.10.203:7005
2018-09-20 10:46:57,203 [lettuce-nioEventLoop-6-16] INFO - Reconnected to 192.168.10.11:7000
2018-09-20 10:46:57,203 [lettuce-nioEventLoop-6-1] INFO - Reconnected to 192.168.10.159:7003
2018-09-20 10:46:57,203 [lettuce-nioEventLoop-6-2] INFO - Reconnected to 192.168.10.159:7000
2018-09-20 10:46:57,203 [lettuce-nioEventLoop-6-3] INFO - Reconnected to 192.168.10.203:7005
2018-09-20 10:46:57,203 [lettuce-nioEventLoop-6-4] INFO - Reconnected to 192.168.10.203:7004
2018-09-20 10:46:57,203 [lettuce-nioEventLoop-6-5] INFO - Reconnected to 192.168.10.203:7005
2018-09-20 10:46:57,302 [lettuce-eventExecutorLoop-4-14] INFO - Reconnecting, last destination was /192.168.10.11:7002
2018-09-20 10:46:57,302 [lettuce-eventExecutorLoop-4-2] INFO - Reconnecting, last destination was /192.168.10.203:7002
2018-09-20 10:46:57,302 [lettuce-eventExecutorLoop-4-1] INFO - Reconnecting, last destination was /192.168.10.89:7004
2018-09-20 10:46:57,302 [lettuce-eventExecutorLoop-4-15] INFO - Reconnecting, last destination was /192.168.10.89:7003
2018-09-20 10:46:57,302 [lettuce-eventExecutorLoop-4-16] INFO - Reconnecting, last destination was /192.168.10.203:7000
2018-09-20 10:46:57,302 [lettuce-nioEventLoop-6-6] INFO - Reconnected to 192.168.10.11:7002
2018-09-20 10:46:57,302 [lettuce-nioEventLoop-6-10] INFO - Reconnected to 192.168.10.203:7000
2018-09-20 10:46:57,303 [lettuce-nioEventLoop-6-8] INFO - Reconnected to 192.168.10.89:7004
2018-09-20 10:46:57,303 [lettuce-nioEventLoop-6-7] INFO - Reconnected to 192.168.10.203:7002
2018-09-20 10:46:57,303 [lettuce-nioEventLoop-6-9] INFO - Reconnected to 192.168.10.89:7003
2018-09-20 10:46:57,402 [lettuce-eventExecutorLoop-4-3] INFO - Reconnecting, last destination was /192.168.10.89:7000
2018-09-20 10:46:57,402 [lettuce-eventExecutorLoop-4-4] INFO - Reconnecting, last destination was /192.168.10.89:7000
2018-09-20 10:46:57,402 [lettuce-eventExecutorLoop-4-5] INFO - Reconnecting, last destination was /192.168.10.11:7000
2018-09-20 10:46:57,403 [lettuce-nioEventLoop-6-11] INFO - Reconnected to 192.168.10.89:7000
2018-09-20 10:46:57,403 [lettuce-nioEventLoop-6-12] INFO - Reconnected to 192.168.10.89:7000
2018-09-20 10:46:57,403 [lettuce-nioEventLoop-6-13] INFO - Reconnected to 192.168.10.11:7000
2018-09-20 10:46:57,502 [lettuce-eventExecutorLoop-4-6] INFO - Reconnecting, last destination was /192.168.10.11:7000
2018-09-20 10:46:57,502 [lettuce-eventExecutorLoop-4-8] INFO - Reconnecting, last destination was /192.168.10.89:7003
2018-09-20 10:46:57,502 [lettuce-eventExecutorLoop-4-7] INFO - Reconnecting, last destination was /192.168.10.11:7002
2018-09-20 10:46:57,503 [lettuce-nioEventLoop-6-16] INFO - Reconnected to 192.168.10.11:7002
2018-09-20 10:46:57,503 [lettuce-nioEventLoop-6-14] INFO - Reconnected to 192.168.10.11:7000
2018-09-20 10:46:57,503 [lettuce-nioEventLoop-6-15] INFO - Reconnected to 192.168.10.89:7003
2018-09-20 10:46:57,602 [lettuce-eventExecutorLoop-4-10] INFO - Reconnecting, last destination was /192.168.10.159:7000
2018-09-20 10:46:57,602 [lettuce-eventExecutorLoop-4-9] INFO - Reconnecting, last destination was /192.168.10.11:7002
2018-09-20 10:46:57,603 [lettuce-nioEventLoop-6-1] INFO - Reconnected to 192.168.10.159:7000
2018-09-20 10:46:57,603 [lettuce-nioEventLoop-6-2] INFO - Reconnected to 192.168.10.11:7002
2018-09-20 10:46:57,703 [lettuce-eventExecutorLoop-4-11] INFO - Reconnecting, last destination was /192.168.10.203:7005
2018-09-20 10:46:57,703 [lettuce-nioEventLoop-6-3] INFO - Reconnected to 192.168.10.203:7005
2018-09-20 10:46:57,803 [lettuce-eventExecutorLoop-4-12] INFO - Reconnecting, last destination was /192.168.10.11:7002
2018-09-20 10:46:57,803 [lettuce-nioEventLoop-6-4] INFO - Reconnected to 192.168.10.11:7002```Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:15 (5 by maintainers)
Top Results From Across the Web
What does lettuce mean by long lived connections?
Does lettuce just rely on reconnecting instead of running a periodic command like PING to keep the redis connection alive?
Read more >Lettuce Reference Guide
This is because all I/O and command processing are handled asynchronously using the netty EventLoop. Connecting to Redis is insanely simple:.
Read more >Lots of connection errors (without secret stuff in it!)
isn't an error, it's an INFO log message that lettuce tries to reconnect to your Redis server. It seems the shaded artifact has...
Read more >lettuce-io/Lobby - Gitter
Lettuce does not resolve InetSockAddresses to avoid blocking. Therefore you see unresolved . The resolution happens during the connect phase.
Read more >Introduction to Lettuce - the Java Redis Client - Baeldung
This article is an introduction to Lettuce, a Redis Java client. ... will maintain its connection to the server and reconnect if needed....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
聊出母语~~
@gppwin @greenHard Please do not use Chinese (or other foreign languages) in a GitHub issue for a global FOSS project; it makes it very hard for the rest of us to participate in the discussion.