791319 - Upgrade b2 cluster in scl3 to MySQL 5.1 and put into puppet

Status: RESOLVED FIXED

(Data & BI Services Team :: DB: MySQL, task)

Description

[Sheeri Cabral [:sheeri]]

Currently b2 is MySQL 5.0.

Comment 1

[Sheeri Cabral [:sheeri]]

And it's not innodb_file_per_table, not with a 24 Gb ibdata file!

Comment 2

[Sheeri Cabral [:sheeri]]

Took tp-b02-slave01 out of the load balancer, downtime'd in nagios for 2.5 hours, stopped the slave and am doing a mysqldump --all-databases now.

When that's done, I will remove the MySQL packages, move aside the /var/lib/mysql and /var/lib/mysql-innodb directories and then upgrade to Percona 5.1 by putting into puppet, and then importing the export and doing a mysql_upgrade.

Comment 3

[Sheeri Cabral [:sheeri]]

ack, this should really be in bug 790409!

Comment 4

[Sheeri Cabral [:sheeri]]

That's odd, b2-db1 is up to date, but b2-db2 is not:

mysql> select @@hostname, @@version;
+----------------------------+--------------------+
| @@hostname                 | @@version          |
+----------------------------+--------------------+
| b2-db1.db.scl3.mozilla.com | 5.1.65-rel14.0-log |
+----------------------------+--------------------+
1 row in set (0.00 sec)

mysql> select @@hostname, @@version;
+----------------------------+------------+
| @@hostname                 | @@version  |
+----------------------------+------------+
| b2-db2.db.scl3.mozilla.com | 5.0.77-log | 
+----------------------------+------------+
1 row in set (0.00 sec)

I just double-checked, and b2-db2 is just a regular slave. Moving b2-db2 to be out of the load balancer pool.

Comment 5

[Sheeri Cabral [:sheeri]]

b2-db2 is upgraded; both b2-db1 and b2-db2 are in puppet as well. Huzzah!