Bug #93099 when a slave is promoted to master and master to slave, the new DBs not replicat
Submitted: 6 Nov 2018 16:39 Modified: 7 Nov 2018 16:07
Reporter: Sibel Kamer Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.6.42 OS:Red Hat
Assigned to: Bogdan Kecman CPU Architecture:Any

[6 Nov 2018 16:39] Sibel Kamer

We have a massive standalone MySQL 5.6 db(call it serverA) -close to 1TB and needs to be available 24/7-  which we have to upgrade to 5.7 
While investigating upgrade options, I thought maybe using master-slave replication where A will be the master and then promoting the slave to be the new master -once it is upgraded to 5.7- and then upgrade serverA -as it is slave now.
I was doing some tests on 2 small VMs with dummy DBs and when I promoted the slave to be the new master and old master to be the new slave, new DBs created on the new master are not replicated to new slave. The problem doesnt happen when updating existing dbs/tables.
I am new to MySQL replication and I dont know if it is an expected behavior or not.
Could you please help me with it?
Also, what would be the recommended way for this type of upgrade? It is very tricky as we have limited compute resources as well.

How to repeat:
anytime slave promoted to master and new db created
[7 Nov 2018 16:07] Bogdan Kecman
Please contact MySQL Support team ( https://www.mysql.com/support/ ) or use MySQL Forum ( https://forums.mysql.com/ ) to get help on how to do stuff with mysql. Bugs system is for reporting bugs only, not for asking questions how to do stuff.