gpt4 book ai didi

apache-zookeeper - mesos-master 与 zookeeper 集群崩溃

转载 作者:行者123 更新时间:2023-12-04 08:30:09 24 4
gpt4 key购买 nike

我正在部署一个有 3 个节点的 zookeeper 集群。我用它来保持 mesos master 的高可用性。我下载zookeeper-3.4.6.tar.gz tarball解压到/opt,重命名为/opt/zookeeper,进入目录,编辑conf/zoo.cfg(粘贴如下),在dataDir中创建myid文件(在zoo.cfg中设置为/var/lib/zookeeper),并使用./bin/zkServer.sh start启动zookeeper,一切顺利。我一一启动所有 3 个节点,它们看起来都很好。我使用 ./bin/zkCli.sh 连接服务器,没问题。

但是当我启动mesos时(3个master和3个slave,每个节点运行一个master和一个slave),然后master很快就崩溃了,一个接一个,在网页http://mesos_master:5050 , 从站选项卡,不显示从站。但是当我只运行一个动物园管理员时,这些都很好。所以我认为这是zookeeper集群的问题。

我的 ubuntu 服务器中有 3 个 PV 主机。他们都在运行 ubuntu 14.04 LTS:
节点 01、节点 02、节点 03、
我有 /etc/hosts在像这样的所有三个节点中:

172.16.2.70     node-01
172.16.2.81 node-02
172.16.2.80 node-03

我在所有三个节点上都安装了zookeeper、mesos。 Zookeeper 配置文件是这样的(所有三个节点):
tickTime=2000
dataDir=/var/lib/zookeeper
clientPort=2181
initLimit=5
syncLimit=2
server.1=node-01:2888:3888
server.2=node-02:2888:3888
server.3=node-03:2888:3888

它们可以正常启动并运行良好。然后我使用命令行 ./bin/mesos-master.sh --zk=zk://172.16.2.70:2181,172.16.2.81:2181,172.16.2.80:2181/mesos --work_dir=/var/lib/mesos --quorum=2 启动 mesos-master 服务,几秒钟后,它给了我这样的错误:
F0817 15:09:19.995256  2250 master.cpp:1253] Recovery failed: Failed to recover registrar: Failed to perform fetch within 1mins
*** Check failure stack trace: ***
@ 0x7fa2b8be71a2 google::LogMessage::Fail()
@ 0x7fa2b8be70ee google::LogMessage::SendToLog()
@ 0x7fa2b8be6af0 google::LogMessage::Flush()
@ 0x7fa2b8be9a04 google::LogMessageFatal::~LogMessageFatal()


@ 0x7fa2b81a899a mesos::internal::master::fail()


@ 0x7fa2b8262f8f _ZNSt5_BindIFPFvRKSsS1_EPKcSt12_PlaceholderILi1EEEE6__callIvJS1_EJLm0ELm1EEEET_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE


@ 0x7fa2b823fba7 _ZNSt5_BindIFPFvRKSsS1_EPKcSt12_PlaceholderILi1EEEEclIJS1_EvEET0_DpOT_
@ 0x7fa2b820f9f3 _ZZNK7process6FutureI7NothingE8onFailedISt5_BindIFPFvRKSsS6_EPKcSt12_PlaceholderILi1EEEEvEERKS2_OT_NS2_6PreferEENUlS6_E_clES6_
@ 0x7fa2b826305c _ZNSt17_Function_handlerIFvRKSsEZNK7process6FutureI7NothingE8onFailedISt5_BindIFPFvS1_S1_EPKcSt12_PlaceholderILi1EEEEvEERKS6_OT_NS6_6PreferEEUlS1_E_E9_M_invokeERKSt9_Any_dataS1_
@ 0x4a44e7 std::function<>::operator()()
@ 0x49f3a7 _ZN7process8internal3runISt8functionIFvRKSsEEJS4_EEEvRKSt6vectorIT_SaIS8_EEDpOT0_
@ 0x499480 process::Future<>::fail()
@ 0x7fa2b806b4b4 process::Promise<>::fail()
@ 0x7fa2b826011b process::internal::thenf<>()
@ 0x7fa2b82a0757 _ZNSt5_BindIFPFvRKSt8functionIFN7process6FutureI7NothingEERKN5mesos8internal8RegistryEEERKSt10shared_ptrINS1_7PromiseIS3_EEERKNS2_IS7_EEESB_SH_St12_PlaceholderILi1EEEE6__callIvISM_EILm0ELm1ELm2EEEET_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
@ 0x7fa2b82962d9 std::_Bind<>::operator()<>()
@ 0x7fa2b827ee89 std::_Function_handler<>::_M_invoke()
I0817 15:09:20.098639 2248 http.cpp:283] HTTP GET for /master/state.json from 172.16.2.84:54542 with User-Agent='Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36'
@ 0x7fa2b8296507 std::function<>::operator()()
@ 0x7fa2b827efaf _ZZNK7process6FutureIN5mesos8internal8RegistryEE5onAnyIRSt8functionIFvRKS4_EEvEES8_OT_NS4_6PreferEENUlS8_E_clES8_
@ 0x7fa2b82a07fe _ZNSt17_Function_handlerIFvRKN7process6FutureIN5mesos8internal8RegistryEEEEZNKS5_5onAnyIRSt8functionIS8_EvEES7_OT_NS5_6PreferEEUlS7_E_E9_M_invokeERKSt9_Any_dataS7_
@ 0x7fa2b8296507 std::function<>::operator()()
@ 0x7fa2b82e4419 process::internal::run<>()
@ 0x7fa2b82da22a process::Future<>::fail()
@ 0x7fa2b83136b5 std::_Mem_fn<>::operator()<>()
@ 0x7fa2b830efdf _ZNSt5_BindIFSt7_Mem_fnIMN7process6FutureIN5mesos8internal8RegistryEEEFbRKSsEES6_St12_PlaceholderILi1EEEE6__callIbIS8_EILm0ELm1EEEET_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
@ 0x7fa2b8307d7f _ZNSt5_BindIFSt7_Mem_fnIMN7process6FutureIN5mesos8internal8RegistryEEEFbRKSsEES6_St12_PlaceholderILi1EEEEclIJS8_EbEET0_DpOT_
@ 0x7fa2b82fe431 _ZZNK7process6FutureIN5mesos8internal8RegistryEE8onFailedISt5_BindIFSt7_Mem_fnIMS4_FbRKSsEES4_St12_PlaceholderILi1EEEEbEERKS4_OT_NS4_6PreferEENUlS9_E_clES9_
@ 0x7fa2b830f065 _ZNSt17_Function_handlerIFvRKSsEZNK7process6FutureIN5mesos8internal8RegistryEE8onFailedISt5_BindIFSt7_Mem_fnIMS8_FbS1_EES8_St12_PlaceholderILi1EEEEbEERKS8_OT_NS8_6PreferEEUlS1_E_E9_M_invokeERKSt9_Any_dataS1_
@ 0x4a44e7 std::function<>::operator()()
@ 0x49f3a7 _ZN7process8internal3runISt8functionIFvRKSsEEJS4_EEEvRKSt6vectorIT_SaIS8_EEDpOT0_
@ 0x7fa2b82da202 process::Future<>::fail()
@ 0x7fa2b82d2d82 process::Promise<>::fail()
Aborted

有时警告是这样的,然后与上面相同的输出崩溃:
0817 15:09:49.745750  2104 recover.cpp:111] Unable to finish the recover protocol in 10secs, retrying

我想知道zookeeper是否在我的情况下部署并运行良好,以及如何定位问题所在。欢迎任何答案和建议。谢谢。

最佳答案

实际上,就我而言,这是因为我没有打开防火墙端口 5050 以允许三台服务器相互通信。更新防火墙规则后,它开始按预期工作。

关于apache-zookeeper - mesos-master 与 zookeeper 集群崩溃,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/32044884/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com