Re: MySQL Replication - promote slave

2011-06-22 Thread Matthias Urlichs
Hi, > 1. flush logs on the master (only if it's accessible, of course). > Not really necessary if you block clients (firewall rule for new connections to port 3306?). Anyway, why don't you use a dual-master setup? I find that this is a whole lot easier to administer than a master/ fallback-slav

Re: MySQL Replication - promote slave

2011-06-22 Thread Radoulov, Dimitre
On 22/06/2011 15:21, Matthias Urlichs wrote: Hi, 1. flush logs on the master (only if it's accessible, of course). Not really necessary if you block clients (firewall rule for new connections to port 3306?). Hi Matthias, thank you for replying! Isn't the flush logs command necessary in or

MySQL Replication - promote slave

2011-06-21 Thread Radoulov, Dimitre
Hi all, I need to document the switch between master and slave and I want to double check if the outlined procedure is correct. We have a simple master slave replication setup on OEL 5.5 and MySQL 5.5.13. Original config: machineA master, machineB slave. Target: machineB master, machineA not