This DB is currently being used by bugzilla-stage and bugzilla-stage-tip, we should upgrade this to 5.5 in preparation of Bugzilla moving to RHEL 6/4.2 and SCL3. We should co-ordinate with the Bugzilla Devs for this.

glob/dkl - r? Basically, we're already running RHEL 6.x on these DB servers. We will upgrade the MySQL version on this to MariaDB 5.5 as we prepare to move Bugzilla prod to SCL3 + 4.2

What is the diff with Percona and MariaDB? and why are we moving to the latter if we just upgraded to the former in production? dave "not a db expert" lawrence

I'll let sheeri answer the why (now that you've asked, I'm curious too but have no clue :p), but Percona is only the current prod. The new prod in SCL3 will be Maria too (so everything will be in sync).

Percona is not backwards-compatible with Oracle's MySQL, but MariaDB is. Plus MariaDB is in general a better community steward (though not perfect) - not just politically, but they send their patches back to Oracle for inclusion, Percona does not. Also, Percona's build is a patch set - they take the Google/Facebook patches and their InnoDB storage engine. It's not a full-fledged fork. MariaDB is. So if in some alternate dimension, Oracle ever did kill off MySQL, MariaDB would be the software to use. I was on the fence about MariaDB when I started the upgrade months ago, but as I learned more about MariaDB and Percona, I thought MariaDB was the best way to go. BTW, the reason we're not going with Oracle's MySQL build is that both the Percona and MariaDB builds add extra features. Now, with MariaDB changing their numbering around - http://blog.mariadb.org/explanation-on-mariadb-10-0/ - and basically saying they have too many new features, we may switch back to Oracle for MySQL 5.6. I always want to be able to have the choice to migrate to other software if needed. But for now, the priority is to get off MySQL 5.0 :D

is "bugzilla1/2.db.scl3.mozilla.com" accurate or are we talking about a stage cluster here?

My bad, this is for stage. Updated the subject. Please get a go ahead from the Bugzilla devs before we do this. Thanks for clarifying sheeri!

To double confirm : This bug is for bugzilla1.stage.db.scl3.mozilla.com and bugzilla2.stage.db.scl3.mozilla.com

Sunday evening, monday morning glob time, is fine with me. We will need the staging environment for production push tonight/tomorrow so this week is not good. dkl

(In reply to David Lawrence [:dkl] from comment #8) > Sunday evening, monday morning glob time, is fine with me. We will need the > staging environment for production push tonight/tomorrow so this week is not > good. +1, although i won't be online monday morning (or any morning).

So, is Monday morning Sheeri time (Eastern US time, GMT-4 right now) OK?

(In reply to Sheeri Cabral [:sheeri] from comment #10) > So, is Monday morning Sheeri time (Eastern US time, GMT-4 right now) OK? Yes

bugzilla2 upgraded to MariaDB 5.5

bugzilla1 has been upgraded. Will take off downtimes and put load balancer back to the way it was.

Nagios downtimes are off and the load balancer is back to the way it was, but I need to open a bug to check replication on these servers.

Resolving, I have made bug 790375 for this.