zhangzhiguang2 opened a new issue #1465: URL: https://github.com/apache/shardingsphere-elasticjob/issues/1465
This problem has troubled me for three days. The specific error is as follows: 2020-09-17 11:55:13.692 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:1032 - Opening socket connection to server 192.168.13.25/192.168.13.25:2181. Will not attempt to authenticate using SASL (unknown error) 2020-09-17 11:55:13.693 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:876 - Socket connection established to 192.168.13.25/192.168.13.25:2181, initiating session 2020-09-17 11:55:13.793 [Curator-Framework-0-EventThread] INFO org.apache.zookeeper.ClientCnxn:519 - EventThread shut down for session: 0x0 2020-09-17 11:55:13.793 [Curator-Framework-0] INFO org.apache.zookeeper.ZooKeeper:684 - Session: 0x0 closed 2020-09-17 11:55:13.793 [Curator-Framework-0] INFO org.apache.zookeeper.ZooKeeper:438 - Initiating client connection, connectString=192.168.13.25:2181 sessionTimeout=3000 watcher=org.apache.curator.ConnectionState@321ef649 2020-09-17 11:55:13.794 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:1032 - Opening socket connection to server 192.168.13.25/192.168.13.25:2181. Will not attempt to authenticate using SASL (unknown error) 2020-09-17 11:55:13.794 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:876 - Socket connection established to 192.168.13.25/192.168.13.25:2181, initiating session 2020-09-17 11:55:13.795 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:1158 - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect 2020-09-17 11:55:13.798 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:1032 - Opening socket connection to server 192.168.13.25/192.168.13.25:2181. Will not attempt to authenticate using SASL (unknown error) 2020-09-17 11:55:13.798 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:876 - Socket connection established to 192.168.13.25/192.168.13.25:2181, initiating session 2020-09-17 11:55:13.798 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:1158 - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect 2020-09-17 11:55:13.815 [Curator-Framework-0] WARN org.apache.curator.ConnectionState:194 - Connection attempt unsuccessful after 3332 (greater than max timeout of 3000). Resetting connection and trying again with a new connection. 2020-09-17 11:55:13.899 [Curator-Framework-0-EventThread] INFO org.apache.zookeeper.ClientCnxn:519 - EventThread shut down for session: 0x0 2020-09-17 11:55:13.899 [Curator-Framework-0] INFO org.apache.zookeeper.ZooKeeper:684 - Session: 0x0 closed 2020-09-17 11:55:13.899 [Curator-Framework-0] INFO org.apache.zookeeper.ZooKeeper:438 - Initiating client connection, connectString=192.168.13.25:2181 sessionTimeout=3000 watcher=org.apache.curator.ConnectionState@230bb7b4 2020-09-17 11:55:13.899 [Curator-Framework-0-SendThread(192.168.13.25:2181)] INFO org.apache.zookeeper.ClientCnxn:1032 - Opening socket connection to server 192.168.13.25/192.168.13.25:2181. Will not attempt to authenticate using SASL (unknown error) Moreover, when the task is running for 1 to 2 days, the task suddenly does not run, and zk suddenly reports an error, and there is no way. How can I solve this problem? Is there a better solution? zk configuration : maxClientCnxns=60 tickTime=2000 initLimit=10 syncLimit=5 dataDir=/data/ivory/south/zookeeper/data clientPort=2181 admin.serverPort=8081 autopurge.purgeInterval=6 server.1=192.168.13.25:2888:3888 server.6=192.168.13.43:2888:3888 server.4=192.168.13.42:2888:3888 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
