CuratorFrameworkImpl - 后台异常不可重试或重试放弃

问题描述 投票:0回答:2

Curator 框架版本 - 4.3.0,Zookeeper 版本 - 5.5.0

我们在 Kubernetes 上部署了 apache atlas,它使用 Zookeeper 从两个 atlas pod 中选出一个作为领导者。 我们正在运行三个 zookeeper pod(3 节点集群),一个 pod 宕机应该不会造成任何问题。当一个 zookeeper pod 宕机时,zookeeper 集群仍然健康,并且有一个 zookeeper leader 可用。我通过执行到 zookeeper pod 并检查 zookeeper 状态来测试它。 但是策展人框架抛出以下错误-

[main:] ~ Background exception was not retry-able or retry gave up (CuratorFrameworkImpl:685)
java.net.UnknownHostException: zookeeper-2.zookeeper-headless.atlas.svc.cluster.local: Name or service not known
    at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
    at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
    at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
    at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
    at java.net.InetAddress.getAllByName(InetAddress.java:1193)
    at java.net.InetAddress.getAllByName(InetAddress.java:1127)
    at org.apache.zookeeper.client.StaticHostProvider.<init>(StaticHostProvider.java:61)
    at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:445)
    at org.apache.curator.utils.DefaultZookeeperFactory.newZooKeeper(DefaultZookeeperFactory.java:29)
    at org.apache.curator.framework.imps.CuratorFrameworkImpl$2.newZooKeeper(CuratorFrameworkImpl.java:196)
    at org.apache.curator.HandleHolder$1.getZooKeeper(HandleHolder.java:101)
    at org.apache.curator.HandleHolder.getZooKeeper(HandleHolder.java:57)
    at org.apache.curator.ConnectionState.reset(ConnectionState.java:201)
    at org.apache.curator.ConnectionState.start(ConnectionState.java:111)
    at org.apache.curator.CuratorZookeeperClient.start(CuratorZookeeperClient.java:214)
    at org.apache.curator.framework.imps.CuratorFrameworkImpl.start(CuratorFrameworkImpl.java:314)
    at org.apache.atlas.web.service.CuratorFactory.initializeCuratorFramework(CuratorFactory.java:88)
    at org.apache.atlas.web.service.CuratorFactory.<init>(CuratorFactory.java:78)
    at org.apache.atlas.web.service.CuratorFactory.<init>(CuratorFactory.java:73)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1152)

zookeeperConnectionString = "zookeeper-0.zookeeper-headless.atlas.svc.cluster.local:2181,zookeeper-1.zookeeper-headless.atlas.svc.cluster.local:2181,zookeeper-2.zookeeper-headless。 atlas.svc.cluster.local:2181"

我们面临的问题是,当我们尝试运行 leaderLatch.start() 它不会返回任何错误,但相应的 znode 没有在 zookeeper 中创建。

apache-zookeeper apache-curator apache-atlas
2个回答
0
投票

您看到错误的原因是在 Kubernetes 上重新启动 pod 时,它的 DNS 记录也会在短时间内被删除,直到 pod 再次出现。在你的情况下,不会有问题,因为策展人将连接到你 CS 中的另一个 ZK 服务器。


0
投票

DNS 记录审查/清理对同一问题没有帮助。

我会推荐你帮助我 https://github.com/apache/shardingsphere/issues/19079

© www.soinside.com 2019 - 2024. All rights reserved.