mesoscloud / mesos-master

Mesos Master
https://hub.docker.com/r/mesoscloud/mesos-master/
MIT License
15 stars 16 forks source link

Unable to finish the recover protocol when using Zookeeper #9

Open YZLRYO opened 7 years ago

YZLRYO commented 7 years ago

I start one Zookeeper Quorum node and one mesos-master node, when joining in Zookeeper cluster, issues happened as logs show:

roup process (group(4)@192.168.xx.xxx:5050) connected to ZooKeeper I0314 02:05:31.871304 11 group.cpp:831] Syncing group operations: queue size (joins, cancels, datas) = (0, 0, 0) I0314 02:05:31.871312 11 group.cpp:427] Trying to create path '/mesos' in ZooKeeper I0314 02:05:31.877079 15 contender.cpp:263] New candidate (id='4') has entered the contest for leadership I0314 02:05:31.878131 12 network.hpp:413] ZooKeeper group memberships changed I0314 02:05:31.878303 11 detector.cpp:152] Detected a new leader: (id='4') I0314 02:05:31.878255 10 group.cpp:700] Trying to get '/mesos/log_replicas/0000000003' in ZooKeeper I0314 02:05:31.878422 11 group.cpp:700] Trying to get '/mesos/json.info_0000000004' in ZooKeeper I0314 02:05:31.882832 11 detector.cpp:479] A new leading master (UPID=master@192.168.xxx.xxx:5050) is detected I0314 02:05:31.883616 13 master.cpp:1711] The newly elected leader is master@192.168.xxx.xxx:5050 with id 6fcd7 I0314 02:05:31.883729 13 master.cpp:1724] Elected as the leading master! I0314 02:05:31.883747 13 master.cpp:1469] Recovering from registrar I0314 02:05:31.883785 10 network.hpp:461] ZooKeeper group PIDs: { log-replica(1)@192.168.xxx.xxx:5050 } I0314 02:05:31.884357 13 registrar.cpp:307] Recovering registrar 2017-03-14 02:05:35,225:9(0x7f76615ef700):ZOO_WARN@zookeeper_interest@1557: Exceeded deadline by 14ms 2017-03-14 02:05:35,225:9(0x7f76625f1700):ZOO_WARN@zookeeper_interest@1557: Exceeded deadline by 13ms 2017-03-14 02:05:35,226:9(0x7f7643238700):ZOO_WARN@zookeeper_interest@1557: Exceeded deadline by 13ms I0314 02:05:41.825330 18 recover.cpp:109] Unable to finish the recover protocol in 10secs, retrying