On 7/25/10 3:46 PM, Alex Dean wrote:
On Jul 25, 2010, at 3:03 AM, der.hans wrote:
I'm needing to convert a very busy production myisam table that is
somewhat humongous to innodb and the conversion takes longer than the
maintenance windows.
If you have a slave which is capable of becoming a production server,
you can convert the slave to innodb. Let the conversion process take
as long as it needs. Master is stil myisam, and slave is now
innodb. Then during maintainence window, you take down the master and
bind its IPs to the slave. Now you master is innodb. Needs testing,
of course, but I believe this would work just fine. If you then set
up the old master as a slave to the new master, you'll be able to
switch back to using myisam on your master (as a saftey net).
There is a program in OpenBSd that can help with this. its called carp.
you have 2 machines running, one the primary and the other the backup.
if the main fails, carp kicks in and take possession if the relevant ip
addresses (as far as your network is concerned, you never lost
connectivity). I am not sure of they have a similar command in linux,
but its worth checking on. this in combination with a live running
backup of mysql would mean that you don't have to worry about manually
changing ip's on the other box, it would be done automatically.
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
