On Thu, 31 Mar 2005 [EMAIL PROTECTED] wrote:
>
> We have one master and one slave database and use the slave for reads.
> If for some reason our master goes down,
> we would like to make our slave the master and use it for both writes
> and reads and then switch to the original configuration
> whe
Hi Jalil,
I had the same problem more than once. I solved it
with a (not-so) simple perl script but the idea is
very simple: swap the machines!
scenario #1: master and slave running
- master is used for writes, slave for reads,
replication goes well. you have a DNS entry for
MASTERDB.domain an
I haven't done it in a nice way and I haven't done it in a long time,
but you can do this.
In the past, I've done the following:
On the slave:
1) stop the server
2) comment out all the lines in my.cnf that refer to the machine as
being a slave -- you still need your binary log directives though.
We have one master and one slave database and use the slave for reads.
If for some reason our master goes down,
we would like to make our slave the master and use it for both writes
and reads and then switch to the original configuration
when the master is up, which includes updating the master c
