[MySQL-replication] master to master upgrade 5.0-> 5.1

----- Original Message -----
From: "Database System" <[email protected]>

We know when we upgrade replication servers from 5.0 to 5.1, we need
to upgrade slave server first. But what about master to master
replication?

From: Johan De Meersman <[email protected]>
Subject: Re: master to master upgrade 5.0-> 5.1
To: [email protected]
Cc: "Replication" <[email protected]>
Date: Wednesday, January 4, 2012, 6:14 AM
Strictly speaking, master-master is not supported, so
you're on your own :-)

Given that the new slave speaks both formats (assuming
there's a format change), it makes sense to stop the slave
on the active master; then upgrade the passive master; then
upgrade the active master and then re-enabling the slave on
that node - that way the last slave to be upgraded will only
start reading the new format logs after it has been
upgraded, and everything should work.

You can, of course, switch operations to the passive node
after it's been upgraded, if so desired.

--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

----- Original Message -----
From: "Database System" <[email protected]>

Do all the users databases have to be run through mysql_upgrade?

From: Johan De Meersman <[email protected]>
Subject: Re: master to master upgrade 5.0-> 5.1
To: [email protected]
Cc: "Replication" <[email protected]>
Date: Thursday, January 5, 2012, 7:22 AM
mysql_upgrade?

No. That script acts only on the mysql database. User
databases usually don't need specific actions; but read the
upgrade notices to be sure - sometimes you may want to do
things like upgrade tables to a newer version of the InnoDB
tablespace format, for instance.



--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel