14

MySQL Replication: Move slave to be slave of another slave, without any (or least possible) downtime

view full story
linux-howto

http://serverfault.com – I have the following setup: M1 = Master 1 S1 = Slave 1 S2 = Slave 2 S3 = Slave 3 Where all slaves are replicating directly from M1. I would like to move S2 and S3 to be slaves of S1. I'm not sure about how to do it without any downtime and with replication picking up where it left off. How to I ensure that the slaves continue from the correct point in the logs from their new master without missing any writes or trying to repeat writes that they had already done before the change. One of the slaves is at an offsite location on a relatively slow connection, and it's quite a large DB, so re (HowTos)

grtyyu's picture
Submitted by grtyyu on 01/22/2012 – Made popular on 01/22/2012

Stories similar to MySQL Replication: Move slave to be slave of another slave, without any (or least possible) downtime

I have replication setup as follows

Master A ----> Slave B ------> Slave C \-------> Slave D \------> Slave E - H

I use this setup because I need a local copy at the office server (that is slave C). I don't want to put extra strain on Master A because it's already receiving all of the inserts and extra load from the slaves connections.

Move MySQL master 33 weeks 6 days ago

I currently have a master db server (lets call it db1) and 6 slaves (slave1-6). I've setup a new server (db2) as a slave of db1 and it's in sync.

Is this possible without having to dump to all other slaves at the same time?

Basically I would create a blank database with the 'create database' function on the master and slave. Then I would setup the replication of the DB. I would then do a dump on the master.. would all the inserts during the dump be replicated to the slave?

TIA!

edit: sorry i didn't mean mysqldump..

We have 2 boxes each running 10 redis intances. The instances on box2 are slaves of corresponding instances on box1. Yesterday, there was a downtime in this setup as all master instances started performing BGSAVE at the same time. This was caused as slaves executed SYNC command concurrently.

MySQL Replication A->B->C 23 weeks 7 hours ago

I was setting the MySQL Replication for master -> slave/master -> slave and Replication for master -> slave its works fine but when i have enable this option in my.cnf

log-slave-updates=1

for updating the master bin log my replications is starting be slower and the time

Seconds_Behind_Master

is growing.

MySQL SSL replication 50 weeks 9 hours ago

I'm currently testing MySQL replication over SSL. I have two mysql-slave pairs.

In a master-slave replication environment, what is required to automatically promote the slave as the master if the master goes down. What are common practice used to change the database reference from an application if the heartbeat of the master database is not detected?

Do I need a cluster to achieve this or is simple 2 machine environment sufficient?

I have just setup one master and one slave server, but its not working..

On my website I connect to the slave server and I insert some rows, but they do not appear on the master and vice versa..

I'm a little confused about the difference between a "secondary name server" and a "slave name server" and a "primary name server" and a "master name server"  

I understand that a slave name server queries the master and updates itself based on changes to the master.