790300 - Get rid of MySQL 5.0 everywhere [tracker]

Status: RESOLVED FIXED

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

Comment 1

[Sheeri Cabral [:sheeri]]

Clusters that still run MySQL 5.0:

phx:
bouncer
sfx01
a01
b02
support
c01
ip-admin02.phx.mozilla.com

scl3:
b2
sumotools1.webapp.scl3.mozilla.com 
stage
khan
webdev

Comment 2

[Sheeri Cabral [:sheeri]]

I've created bugs for all the phx servers, still have to make bugs for the scl3 servers. Still, it's a good start.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

From the dependent bugs, here's the status:

phx1 bouncer        bug 790391 MySQL 5.0 -> MySQL 5.1 
phx1 sfx01          bug 790398 MySQL 5.0 -> Decom or MySQL 5.1 
phx1 a01            bug 780954 MySQL 5.0.77 -> MySQL 5.1, if not 5.5 
phx1 b02            bug 790409 ?? -> MySQL 5.1 
phx1 support        bug 785987 MySQL 5.0.77 -> Percona 5.1 
phx1 c01            bug 790413 ?? -> Decom or MySQL 5.1 
phx1 ip-admin02     bug 790414 MySQL 5.0 -> Decom
scl3 b2    
scl3 sumotools1         
scl3 stage          bug 789035 MySQL 5.0 -> Percona 5.1
scl3 khan    
scl3 webdev

Comment 4

[Sheeri Cabral [:sheeri]]

Note the change in a01 - 5.5 is the next step for ALL databases, but we should get on 5.1 everywhere first. Also we're standardizing on Percona for 5.1, and MariaDB for 5.5, and all 5.0 verisons are 5.0.77....

phx1 bouncer        bug 790391 MySQL 5.0.77 -> Percona 5.1 
phx1 sfx01          bug 790398 MySQL 5.0.77 -> Decom or Percona 5.1 
phx1 a01            bug 780954 MySQL 5.0.77 -> Percona 5.1
phx1 b02            bug 790409 MySQL 5.0.77 -> Percona 5.1 
phx1 support        bug 785987 MySQL 5.0.77 -> Percona 5.1 
phx1 c01            bug 790413 MySQL 5.0.77 -> Decom or Percona 5.1 
phx1 ip-admin02     bug 790414 MySQL 5.0.77 -> Decom
scl3 b2             bug 791319 MySQL 5.0.77 -> Percona 5.1
scl3 sumotools1     bug 791313 MySQL 5.0.77 -> Percona 5.1
scl3 stage          bug 789035 MySQL 5.0.77 -> Percona 5.1
scl3 khan           bug 791315 MySQL 5.0.77 -> Percona 5.1
scl3 webdev         bug 791316 MySQL 5.0.77 -> Percona 5.1

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

We'll need to get these scheduled into the regular downtimes, I think?

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

Note that engagement is running mysql-server 5.1, not Percona

Comment 7

[Sheeri Cabral [:sheeri]]

We don't need downtimes, all these machines (except sumotools in scl3) have redundant architectures.

Comment 8

[Sheeri Cabral [:sheeri]]

(In reply to Dustin J. Mitchell [:dustin] from comment #6)
> Note that engagement is running mysql-server 5.1, not Percona

yes, we were on Oracle's 5.1 for a few months, so there are a few mysql 5.1's out there. We're standardizing now :D

Comment 9

[Sheeri Cabral [:sheeri]]

This might be useful for RHEL5 machines.....

https://mana.mozilla.org/wiki/display/SYSADMIN/MySQL+5.0+to+5.1+Upgrade#MySQL5.0to5.1Upgrade-UpgradeNotesonRHEL5

Comment 10

[Sheeri Cabral [:sheeri]]

FWIW, hitting this bug won't be an issue, because I've given the sumo guys until the end of the month to switch to the new sumotools.

Comment 11

[Sheeri Cabral [:sheeri]]

We shut down MySQL yesterday and nobody's really complained, so....we're good! Gonna close this bug.