12 messages in com.mysql.lists.clusterRe: Handling of network partitioning
FromSent OnAttachments
Michael Varlik16 Apr 2008 00:12 
Anatoly Pidruchny16 Apr 2008 10:36 
Jon Stephens16 Apr 2008 11:12 
Pekka Nousiainen16 Apr 2008 11:33 
Anatoly Pidruchny16 Apr 2008 12:06 
Pekka Nousiainen16 Apr 2008 12:27 
Chris Picton18 Apr 2008 03:50 
Pekka Nousiainen18 Apr 2008 03:57 
Anatoly Pidruchny18 Apr 2008 06:09 
Jonathan Miller18 Apr 2008 09:22 
Anatoly Pidruchny21 Apr 2008 13:40 
Jonathan Miller21 Apr 2008 14:10 
Subject:Re: Handling of network partitioning
From:Chris Picton (lis@tangent.co.za)
Date:04/18/2008 03:50:57 AM
List:com.mysql.lists.cluster

On Wed, 2008-04-16 at 20:33 +0200, Pekka Nousiainen wrote:

according to the manual of mysql cluster 5.0, the cluster handles network partitioning in a way that the set of nodes which the management server belongs to becomes the "new" cluster. The remaining nodes are shut down.

This should be corrected.

The set of nodes here is only DB nodes. Mgm node does not belong to either partition.

To act as an "arbitrator" the mgm node must run on a separate host computer which has no DB nodes.

You can run with 2 mgm nodes. Is this a wise idea?

If you get a partition which ends up with one mgm node per partition, will each one think it is master?

Chris