[mailto:bcantw...@firescope.com]
Sent: Wednesday, October 07, 2009 11:12 AM
To: Gavin Towey
Cc: mysql@lists.mysql.com
Subject: Re: Replication recovery
When only one machine dies I do send the new master position info to the
still running slave, and yes, it does the trick.
My main challenge is when A
easy to detect and repair with a daemon script. Even if both
machines die, it'll be a similar scenario.
Regards,
Gavin Towey
-Original Message-
From: Bryan Cantwell [mailto:bcantw...@firescope.com]
Sent: Wednesday, October 07, 2009 10:47 AM
To: mysql@lists.mysql.com
Subject: R
rds,
Gavin Towey
-Original Message-
From: Bryan Cantwell [mailto:bcantw...@firescope.com]
Sent: Wednesday, October 07, 2009 10:47 AM
To: mysql@lists.mysql.com
Subject: Replication recovery
I have 2 - 5.0.51a mysql databases setup in a dual master scenario. A is
master of B and vise versa..
I have 2 - 5.0.51a mysql databases setup in a dual master scenario. A is
master of B and vise versa...
In Linux 2.6.26 (if that matters).
Everything is great while all is running normally. But, when I am
testing the system by creating disasterous scenarios, I find some
challenges I hope to get
...@firescope.com]
Sent: Friday, July 31, 2009 12:51 PM
To: mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Yes I am trying to simulate total failure. In this test case I am using 2
Virtual Machines and I just kill one and then when it comes back I have the
challenge described
-
From: Gavin Towey [mailto:gto...@ffn.com]
Sent: Friday, July 31, 2009 1:21 PM
To: Cantwell, Bryan; mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Bryan,
How are you restarting mysql? In the case a master crashes, it's definitely
common for the slave to miss the fact tha
ssage-
From: Cantwell, Bryan [mailto:bcantw...@firescope.com]
Sent: Friday, July 31, 2009 10:08 AM
To: mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Before I simulate a total server failure, master1 is using binary file
msyql-bin1 position 2231467 and it's slave mas
ssage-
From: Gavin Towey [mailto:gto...@ffn.com]
Sent: Thursday, July 30, 2009 5:08 PM
To: Cantwell, Bryan; mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Hi Bryan,
Please define "out of whack." Tell us exactly what you're doing when you
restart, and what the
scope.com]
Sent: Thursday, July 30, 2009 11:00 AM
To: mysql@lists.mysql.com
Subject: Replication recovery on restart
I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases
both replicating wonderfully. They are configured in a dual master scenario so
that
I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases
both replicating wonderfully. They are configured in a dual master scenario so
that one can take over for the other in my HA environment I've built. All is
working great until... If one or the other box reboots or the
Thanks a lot. I'll try.
- Original Message -
From: "Kishore Jalleda" <[EMAIL PROTECTED]>
To: "古雷" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, March 29, 2006 11:53 PM
Subject: Re: Multiple-Master Replication recovery
> any one of the servers could g
any one of the servers could go down in many ways like
1) disk crash
2) replication failure
3) power failure
4) any hardware component failure
5) OS hang
6) Network failure
7) MYSQL bug
8) table corruption etc ...
9) or just scheduled donwtime
in any case what really matters is the difference
古雷 wrote:
> Hello:
> If I use Multiple-Master Replication with two mysql server, when one of them
> goes down(disk crashed) must I shutdown the good one to recover the
> Multiple-Master Replication ?
I think yes.
Depends on what you mean with "recover the Multiple-Master Replication"
Do you want
Hello:
If I use Multiple-Master Replication with two mysql server, when one of them
goes down(disk crashed) must I shutdown the good one to recover the
Multiple-Master Replication ?
regards,
gu lei
14 matches
Mail list logo
