jodis连接codis集群有问题啊

2020-04-28 19:51:47,541 [myid:4] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection for client /10.10.7.177:60095 which had sessionid 0x47133adfa6a0071
2020-04-28 19:52:12,107 [myid:4] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@192] - Accepted socket connection from /10.10.7.177:60160
2020-04-28 19:52:12,107 [myid:4] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@893] - Client attempting to renew session 0x47133adfa6a0071 at /10.10.7.177:60160
2020-04-28 19:52:12,108 [myid:4] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@645] - Established session 0x47133adfa6a0071 with negotiated timeout 30000 for client /10.10.7.177:60160
2020-04-28 19:52:44,000 [myid:4] - INFO [SessionTracker:ZooKeeperServer@355] - Expiring session 0x47133adfa6a0071, timeout of 30000ms exceeded
2020-04-28 19:52:44,001 [myid:4] - INFO [ProcessThread(sid:4 cport:-1)::PrepRequestProcessor@489] - Processed session termination for sessionid: 0x47133adfa6a0071
2020-04-28 19:52:44,002 [myid:4] - INFO [CommitProcessor:4:NIOServerCnxn@1008] - Closed socket connection for client /10.10.7.177:60160 which had sessionid 0x47133adfa6a0071
2020-04-28 20:26:07,413 [myid:4] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of stream exception
EndOfStreamException: Unable to read additional data from client sessionid 0x0, likely client has closed socket
at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:230)
at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
at java.lang.Thread.run(Thread.java:748)
2020-04-28 20:26:07,413 [myid:4] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection for client /10.10.7.34:33771 (no session established for client)

jodis连接一开始没有问题，但是过一会时间就会报这个错误，导致codis集群直接不可用，大家proxy高可用和负载均衡是怎么做的啊

Il report contiene log di sessione di ZooKeeper provenienti da una connessione jodis a un cluster Codis, ma non indica file sorgente né test. Inizia riproducendo il timeout della connessione e tracciando la configurazione coinvolta di jodis, ZooKeeper e del proxy Codis. Il lavoro è completato quando viene identificato il motivo per cui il cluster diventa non disponibile e viene documentata o verificata una configurazione affidabile del proxy per l’alta disponibilità e il bilanciamento del carico.

Scritto dal modello di indicizzazione a partire dal testo della issue.