[rt-users] DB Problems upgrading to RT 3.8.2 from 3.6.5

[David Hobley]

Jesse, 

Thanks for the suggestion - this is running on a separate test machine with nothing else running on it. Admittedly, it is running in a Xen VM, although this is the only VM on the underlying server and has been allocated both CPUs and all the RAM available. The file system is on the underlying disk, not an image on the underlying filesystem. 

I will try with mysqltuner and get back to you. 

The nightly backups are another option - the dump takes a couple of hours from memory, the reload takes 8. I'll look into that if mysqltuner doesn't help. 

Cheers, 
David 
----- Original Message ----- 
From: "Jesse Vincent" <jesse at bestpractical.com> 
To: "David Hobley" <david.hobley at mionegroup.com> 
Cc: rt-users at lists.bestpractical.com 
Sent: Tuesday, 3 March, 2009 8:34:27 AM GMT +10:00 Brisbane 
Subject: Re: [rt-users] DB Problems upgrading to RT 3.8.2 from 3.6.5 




On Tue, Mar 03, 2009 at 08:23:31AM +1000, David Hobley wrote: 
> If that is the case, then RT is un-upgradeable. Which would be a problem obviously. I can't take out our database for 6 days. Over a weekend, sure. But no more than that. Does anyone have any suggestions as to how I can optimise this at all? 

Hm. I've made this schema change to larger RT instances in much less time. 
How heavily loaded is your database? How much IO contention is there? 

First up, you should make sure you've tuned mysql a bit. 30 minutes with 
mysqltuner can be a night-and-day change. 


How long do your nightly MySQL backups of RT take? Another option might 
be to dump, massage the schema and load. 


-- 
Cheers, 
David Hobley 

IT Manager 
Creators of Miessence, MiVitality and MiEnviron 

Phone: +61 (7) 5582 7020 
Fax: +61 (7) 5539 6719 
USA Fax 1800 840 0827 
Email : david.hobley at mionegroup.com 
Website: www.mionegroup.com 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20090303/2a14fca8/attachment.htm>