我们使用2.3.0版本的curator-framework来连接到pom文件中的zookeeper。
<dependency>
<groupId>org.apache.curator</groupId>
<artifactId>curator-framework</artifactId>
<version>2.3.0</version>
</dependency>
<dependency>
<groupId>org.apache.curator</groupId>
<artifactId>curator-recipes</artifactId>
<version>2.3.0</version>
</dependency>这是在高负载的服务器中使用的,它将数据注入到kafka中很多次,我们会时不时地收到以下错误。我试着用谷歌搜索,但找不到问题的确切原因和解决方案。寻找如何解决这个问题的想法。
ERROR org.apache.curator.ConnectionState: Connection timed out for connection string (xxx.xx.xx.xx:2181, yy.yy.y.y:2181) and timeout (15000) / elapsed (37893)
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss
at org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:191)
at org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:86)
at org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.getZooKeeper(CuratorFrameworkImpl.java:456)
at org.apache.curator.framework.imps.BackgroundSyncImpl.performBackgroundOperation(BackgroundSyncImpl.java:40)
at org.apache.curator.framework.imps.OperationAndData.callPerformBackgroundOperation(OperationAndData.java:65)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:672)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:664)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:55)
at org.apache.curator.framework.imps.CuratorFrameworkImpl$3.call(CuratorFrameworkImpl.java:243)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)发布于 2020-01-31 00:09:35
您可能需要为您的curator客户端调整会话和连接超时。检查CuratorFramework的connectionTimeoutMs和SessionTimeoutMs设置。
根据经验,您的connectionTimeoutMs应该是SessionTimeoutMs除以集群中Zookeeper节点的数量。如果客户端无法使用connectionTimeoutMs连接到其中一个节点,它将尝试连接到另一个节点,直到会话超时。
需要注意的其他设置是重试策略和重试间隔(如果您使用RetryNTimes策略,则值得检查您的sleepBetweenRetries不是太大,并且在connectionTimeoutMs间隔内得到多次重试)。
https://stackoverflow.com/questions/35201293
复制相似问题