zookeeper配置异常，但manager启动未识别其异常状态，仍强制启动
我在配置zookeeper时用了一个老的zoo集群，该集群需要auth认证。当我启动manager进程时，manager日志打印了zoo的认证错误，但manager未识别该错误，而是继续强制启动进程。
Caused by: org.I0Itec.zkclient.exception.ZkException: org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = NoAuth for /otter at org.I0Itec.zkclient.exception.ZkException.create(ZkException.java:68) ~[zkclient-0.10.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.retryUntilConnected(ZkClientx.java:785) ~[shared.common-4.2.17.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.create(ZkClientx.java:404) ~[shared.common-4.2.17.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.createPersistent(ZkClientx.java:323) ~[shared.common-4.2.17.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.createPersistent(ZkClientx.java:333) ~[shared.common-4.2.17.jar:na] at com.alibaba.otter.shared.arbitrate.impl.setl.monitor.NodeMonitor.(NodeMonitor.java:64) ~[shared.arbitrate-4.2.17.jar:na] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.7.0_201] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) ~[na:1.7.0_201] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:1.7.0_201] at java.lang.reflect.Constructor.newInstance(Constructor.java:526) ~[na:1.7.0_201] at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147) ~[spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE] ... 37 common frames omitted Caused by: org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = NoAuth for /otter at org.apache.zookeeper.KeeperException.create(KeeperException.java:113) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.KeeperException.create(KeeperException.java:51) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783) ~[zookeeper-3.4.5+C41.jar:3.4.5-1392090] at org.I0Itec.zkclient.ZkConnection.create(ZkConnection.java:95) ~[zkclient-0.10.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx$2.call(ZkClientx.java:408) ~[shared.common-4.2.17.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx$2.call(ZkClientx.java:404) ~[shared.common-4.2.17.jar:na] at com.alibaba.otter.shared.common.utils.zookeeper.ZkClientx.retryUntilConnected(ZkClientx.java:775) ~[shared.common-4.2.17.jar:na] ... 46 common frames omitted 2019-08-22 15:50:45.209 [] INFO com.alibaba.otter.manager.deployer.JettyEmbedServer - ##Jetty Embed Server is startup! 2019-08-22 15:50:45.209 [] INFO com.alibaba.otter.manager.deployer.OtterManagerLauncher - ## the manager server is running now ......
原提问者Github用户tongsir
写回答
-
可以看到Zookeeper客户端在连接Zookeeper服务端时，由于没有认证信息，导致连接失败，抛出了org.apache.zookeeper.KeeperException$NoAuthException异常。
但是，Otter Manager启动时并未识别该异常，而是继续启动了Manager进程。
这个问题可能是Otter Manager的启动脚本没有正确处理Zookeeper连接异常导致的。建议您检查一下Otter Manager的启动脚本，看看是否有对Zookeeper连接异常的处理逻辑。如果没有，您可以修改启动脚本，加入对Zookeeper连接异常的处理逻辑，例如检查Zookeeper连接是否成功，如果连接失败，则退出Manager进程。
2023-06-16 15:30:10赞同 展开评论 打赏 -
版权声明：本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
