What a pain to get all of my MySQL 4.1.x installations up to MySQL version 5.0.15. First I have to upgrade all my client libraries, then upgrade any dependencies on the 4.1.x libraries (popper, popproxy, php-mysql, pure-ftp, etc) to reference the new library. Then I get to upgrade the MySQL server installations on my mail servers and other places to be 5.0.15 so they can slave from my ‘main’ master correctly.
Needless to say, yesterday, was a day full of upgrading MySQL. I got all of my slaves and clients done by 11pm. Then I started the move to the new MySQL 5.0.15 box running FreeBSD 6. Unfortunately, after all 30GB were copied (45 sec per gig, not bad), my new 5.0.15 process kept signal 11ing and restarting itself. After all that, my replication was screwed up when I moved back to a 4.1.11 master on the original server. Anyway, it was a pain to get slaves back up. I had to dump the data and copy to the slaves and load manually ‘load data from master’ didnt work right on 5.0.15 slave talking to a 4.1.x master.
However, I think I got my settings on my new ‘master’ correctly set. I missed some kernel stack size variables set in /boot/loader.conf
kern.maxdsiz=2147483648
kern.maxssiz=268435456
I tried setting maxdsiz to 3GB..but my machine crashed on boot. So i’ll keep it at 2gb for now.
Now I’m able to successfully run my InnoDB tests on my new master.. no crashing.. all seems to be good. Here’s hoping that tonight wont bring the same bad luck as last night.




