Re: Crash on backup - Max Mether - com.mysql.lists.cluster

11 messages in com.mysql.lists.clusterRe: Crash on backup

From	Sent On	Attachments
Troy Davis	25 Aug 2005 07:29
Stewart Smith	25 Aug 2005 21:20
Troy Davis	26 Aug 2005 06:51
Alex Davies	27 Aug 2005 10:24
Troy Davis	29 Aug 2005 07:10
Alex Davies	29 Aug 2005 09:23
Max Mether	29 Aug 2005 09:41
Alex Davies	29 Aug 2005 11:34
Troy Davis	19 Sep 2005 14:33
Alex Davies	19 Sep 2005 16:57
Max Mether	20 Sep 2005 01:36

Subject:	Re: Crash on backup
From:	Max Mether (ma...@mysql.com)
Date:	09/20/2005 01:36:05 AM
List:	com.mysql.lists.cluster

Hello Troy,

I'm now preparing to upgrade from 4.1.12-1 rpms to 4.1.14, or whatever is newest. I'd like to minimize downtime, of course. Do you think this will work?

1. "start backup" on the management server without creating or deleting any tables while it runs. 2. Download all RPMs needed for upgrade to each node.

I would download everything before taking the backup, but that's just cosmetic.

3. Shut down management server. 4. Shut down one ndbd node and mysql instance.

This won't work if you have 2 data nodes. You need to have the management server up when you shut down the first node. Otherwise the second node will stop as there is no arbitrator present.

5. Upgrade all RPMs on the node that is shut down. 6. Copy the ndb_mgm binary to management server. 7. Start the management server. 8. Start the first node's ndbd and mysql instances. 9. Wait until the first node recovers its data from other nodes. 10. For each remaining node, shut down its ndbd and mysql processes, upgrade the RPMs, then start the instances. Be sure to allow each node to fully recover data before moving to the next node.

Otherwise it looks good.

Max