15 messages in com.mysql.lists.clusterRe: Clarification on --initial
FromSent OnAttachments
Wilersh13 Aug 2007 09:00 
Geert Vanderkelen13 Aug 2007 09:13 
Wilersh13 Aug 2007 09:22 
Jon Stephens13 Aug 2007 12:06 
Sebastien LELIEVRE13 Aug 2007 23:55 
Geert Vanderkelen14 Aug 2007 00:51 
Geert Vanderkelen14 Aug 2007 00:54 
Max Mether14 Aug 2007 03:14 
Sebastien LELIEVRE16 Aug 2007 00:36 
Geert Vanderkelen16 Aug 2007 03:38 
Al16 Aug 2007 09:57 
Philipp Taprogge16 Aug 2007 10:53 
Anatoly Pidruchny16 Aug 2007 11:16 
Stewart Smith16 Aug 2007 18:47 
Jon Stephens17 Aug 2007 09:12 
Subject:Re: Clarification on --initial
From:Sebastien LELIEVRE (slel@tbs-internet.com)
Date:08/16/2007 12:36:34 AM
List:com.mysql.lists.cluster

Geert Vanderkelen a écrit :

On 14 Aug 2007, at 08:55, Sebastien LELIEVRE wrote:

OR when you bring a brand new data node (as a replacement for a crashed one for instance) in the cluster

You don't have to use --initial for that either. If the data is not there, it will either resync from it's partner or make a new empty filesystem automatically. The '--initial' option is not needed.

that is if your not changing the Cluster configuration.

In the scenarion where A and B are data nodes, if I lose B and have to bring a brand new data node C which has a different IP address, I have to alter the MGM config.ini (even if I give C the same Id than B)

By doing that, mgm will warn me to start the data node C with '--initial' since it can't do nothing with it. Once I've done that, the data node C will sync with A until it can be declared 'started'.

This is a procedure we've tested last week. We couldn't do otherwise, but maybe there is a better way ?

Best Regards,

Sebastien.