Hi All, I did step 1 below and check logs from the new started mesos-master, and it continuously complaint like below.
``` I1125 17:42:59.066706 2330 recover.cpp:188] Received a recover response from a replica in EMPTY status I1125 17:43:09.065188 2331 recover.cpp:111] Unable to finish the recover protocol in 10secs, retrying I1125 17:43:09.066992 2330 replica.cpp:638] Replica in EMPTY status received a broadcasted recover request I1125 17:43:09.067425 2324 recover.cpp:188] Received a recover response from a replica in EMPTY status I1125 17:43:19.067332 2331 recover.cpp:111] Unable to finish the recover protocol in 10secs, retrying I1125 17:43:19.069587 2323 replica.cpp:638] Replica in EMPTY status received a broadcasted recover request I1125 17:43:19.069807 2323 recover.cpp:188] Received a recover response from a replica in EMPTY status ``` Seems it can not catch up the other replicas? -- Thanks, Chengwei On Tue, Nov 24, 2015 at 09:47:16AM +0800, Chengwei Yang wrote: > Hi all, > > We're using mesos in product on CentOS 6 and plan to upgrade CentOS to 7.1, to > avoid affect any tasks running on mesos. We're about to replace all > mesos-masters in fly. > > The procedure listed below: > > 0. 3 mesos-masters running on CentOS 6 > 1. shutdown 1 mesos-master(CentOS 6) and bring up 1 mesos-master(CentOS 7) > wait the new master synced for some time(is there any simple way to know > when?) > 2. repeat step 1 > > NOTE: we plan to shutdown non-leader first, and shutdown the leader(CentOS 6) > last. > > Can we do this in such way? Or any other better suggestions? > > -- > Thanks, > Chengwei
signature.asc
Description: Digital signature
