On Tue, Nov 24, 2015 at 3:38 PM, Marco Massenzio wrote:
> The closest I could find is [0], but granted, much more detail could be
> desirable :)
Agreed! See also https://issues.apache.org/jira/browse/MESOS-3995
Neil
JFYI.
I finished the mesos-master migrate and all works fine as expectd.
--
Thanks,
Chengwei
On Wed, Nov 25, 2015 at 06:29:54PM +0800, Chengwei Yang wrote:
> OOPS,
>
> We forgot to disable firewalld on the new centos7 VM, once firewalld disabled,
> replicate finished in seconds.
>
> as below.
OOPS,
We forgot to disable firewalld on the new centos7 VM, once firewalld disabled,
replicate finished in seconds.
as below.
```
I1125 18:27:33.737843 2490 replica.cpp:369] Replica ignoring promise request
as it is in RECOVERING status
I1125 18:27:33.740927 2489 replica.cpp:655] Replica rece
while the other 2 mesos-master (one leader and one follower) both repeat below
log.
I1125 18:06:33.315208 28401 replica.cpp:638] Replica in VOTING status received
a broadcasted recover request
I1125 18:06:43.316341 28404 replica.cpp:638] Replica in VOTING status received
a broadcasted recover re
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 rec
On 2015/11/25 13:57, Joe Smith wrote:
In retrospect I should've (might still be able to one of these days)
open sourced the tool we used to migrate mesos masters.
btw, it's great!
I will have a try on this.
overall the process suggested so far is correct.
To validate the new host joining, y
On 2015/11/25 13:57, Joe Smith wrote:
In retrospect I should've (might still be able to one of these days)
open sourced the tool we used to migrate mesos masters. That said,
overall the process suggested so far is correct.
To validate the new host joining, you can tail the master log file for
In retrospect I should've (might still be able to one of these days) open
sourced the tool we used to migrate mesos masters. That said, overall the
process suggested so far is correct.
To validate the new host joining, you can tail the master log file for
"Successfully
joined the Paxos group
On Tue, Nov 24, 2015 at 03:38:56PM -0800, Marco Massenzio wrote:
> The closest I could find is [0], but granted, much more detail could be
> desirable :)
> FYI - you may also want to check out the Maintenance Primitives [1] and
> upgrades [2] (which is actually not directly applicable to your state
On 2015/11/24 9:47, 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. shut
The closest I could find is [0], but granted, much more detail could be
desirable :)
FYI - you may also want to check out the Maintenance Primitives [1] and
upgrades [2] (which is actually not directly applicable to your stated use
case, but may be of interest for future reference).
In any event,
Thanks @Tommy,
Since I didn't found any official document about migrate mesos-mater or resize
mesos-master quorum size, so before anything missing that will supprise me,
I came here to confirm. :-)
--
Thanks,
Chengwei
On Wed, Nov 25, 2015 at 12:07:43AM +0800, tommy xiao wrote:
> This is correct
This is correct way on upgrade your mesos cluster, more details see mesos
documents release note.
2015-11-24 9:47 GMT+08:00 Chengwei Yang :
> 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 repl
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
14 matches
Mail list logo