DB Upgrade complete

Mike McGrath mmcgrath at redhat.com
Tue Jul 10 06:56:04 UTC 2007

With the exception cacti (I'll grab it tomorrow), all databases are now 
running off of db2.  The migration went off very well (with one 
exception below).  The total outage lasted about 30 minutes longer than 
expected though all services (except for koji) were only down for a few 
minutes.  For those that aren't familiar, this upgrade was for both 
mysql and postgresql:

mysql-server-3.23.58-1 -> mysql-server-5.0.22-2.1
postgresql-server-7.4.6-2.EL3 -> postgresql-server-8.1.9-1.el5

Considering all of the stuff that could have gone wrong, I'm pretty 
happy.  As always with these things keep your eyes open for any strange 
issues that may pop up.  Right now though all sites seem 'up' and I 
pushed a koji build through.

The one bump we had was an ignorant mistake on my part.  While doing a 
final trial run on db2 before the upgrade (yesterday afternoon) I 
mistook a terminal.  Long story short a table drop and a rm lead to us 
losing all accounts changes between 12:00 and 4:00 p.m. central time.  
(about 4 hours or so).  /me smacks forehead.  If you guys hear anything 
regarding that let me know and we'll work something out (so far all I 
know of is someone had to re-apply for extras-cvs)

So whats left from here? I've updated the ticket:

Here's a summary:

1) Wait a week for db2 so we know its fine
2) I have a few databases left on db1 that I don't *think* are in use.  
I'll be sending those to the list soon for verification.  If we're not 
I'll archive and zip them up.  They were not migrated to the new box.
3) upgrade db1
4) move mysql services back to db1 (it has less ram then db2.  
postgresql is hit much heavier so we'll leave it on the box with more 
processors and ram)
5) Setup a dump from each db to the other.  I'd think 4 times / day 
would be enough, maybe 2 or 3.  We'll have to see how much resources it 
actually takes.

We'll have to do some tweaking.  Toshio pointed out that our postgres 
config is pretty vanilla.  There are probably many tweaks we can do to 
it so I've included it in this email.  I'm a MySQL guy so any assistance 
on the postgres side of things would be appreciated.  If you have any 
questions about our database, our real concern is koji, its the most 
used database in terms of traffic and it is, by far, our largest.

Here's the cacti graphs

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: postgresql.conf
URL: <http://listman.redhat.com/archives/fedora-infrastructure-list/attachments/20070710/e12e96a4/attachment.conf>

More information about the Fedora-infrastructure-list mailing list