redis的超时问题

11:49:29.792 [lettuce-eventExecutorLoop-1-1] INFO  i.l.c.p.ConnectionWatchdog - [log,171] - Reconnecting, last destination was /192.168.0.98:6379

11:49:35.527 [lettuce-nioEventLoop-4-1] INFO  i.l.c.p.ReconnectionHandler - [lambda$null$3,174] - Reconnected to 192.168.0.98/<unresolved>:6379


11:49:29.792 [lettuce-eventExecutorLoop-1-1] INFO  i.l.c.p.ConnectionWatchdog - [log,171] - Reconnecting, last destination was /192.168.0.98:6379

11:49:35.527 [lettuce-nioEventLoop-4-1] INFO  i.l.c.p.ReconnectionHandler - [lambda$null$3,174] - Reconnected to 192.168.0.98/<unresolved>:6379


11:49:29.792 [lettuce-eventExecutorLoop-1-1] INFO  i.l.c.p.ConnectionWatchdog - [log,171] - Reconnecting, last destination was /192.168.0.98:6379

11:49:35.527 [lettuce-nioEventLoop-4-1] INFO  i.l.c.p.ReconnectionHandler - [lambda$null$3,174] - Reconnected to 192.168.0.98/<unresolved>:6379


11:49:29.792 [lettuce-eventExecutorLoop-1-1] INFO  i.l.c.p.ConnectionWatchdog - [log,171] - Reconnecting, last destination was /192.168.0.98:6379

11:49:35.527 [lettuce-nioEventLoop-4-1] INFO  i.l.c.p.ReconnectionHandler - [lambda$null$3,174] - Reconnected to 192.168.0.98/<unresolved>:6379


如果client经常收到这个的话,是因为redis的配置文件中,有一个timeout的配置,意思就是clent空闲多久后就超时,改成0就不会在收到了

Powered By Z-BlogPHP 1.7.4

Copyright 粤ICP备2024347557号 Rights Reserved.