6 messages in com.mysql.lists.clusterRE: MySql Cluster Data Node Failure
FromSent OnAttachments
Waseem Azhar07 Jun 2007 07:09 
Waseem Azhar07 Jun 2007 07:14 
Jimmy Guerrero07 Jun 2007 07:25 
Jon Stephens07 Jun 2007 08:58 
Waseem Azhar08 Jun 2007 00:24 
Sebastien LELIEVRE08 Jun 2007 00:31 
Subject:RE: MySql Cluster Data Node Failure
From:Waseem Azhar (wase@gmail.com)
Date:06/08/2007 12:24:04 AM
List:com.mysql.lists.cluster

Thank You. It was really helpful. I perfom a quick test and it worked.

I have another question, Does it make sense to have more than one Sql Nodes in a cluster. According to my understanding switching between sql nodes is not transparent to the client application. Do i need handle it myself in my client application ? or is there any mechanism exists where if one sql-node goes down the other take up the charge and remain transparent to the client.

Thanks, Azhar.

On 6/7/07, Jimmy Guerrero <jgue@mysql.com> wrote:

Hello,

A data node failure should not bring down a cluster unless it is the last remaining node in a node group.

For example in a four data node cluster, with two replicas configured, you'd have two node groups comprised of two data nodes a piece.

- Node Group 0 * Data Node A * Data Node B

- Node Group 1 * Date Node C * Date Node D

In the above scenario you could loose Data Nodes A and C and still have a fully functional cluster as Data Nodes B and D hold the complete database when combined.

However, if you lost Data Nodes A and B, the cluster would shut down.

Thanks,

Jimmy Guerrero MySQL, Inc

Waseem Azhar wrote:

I have a question to the group .

What if one of my data node goes down for any reason (network connection etc..). Does it mean my whole cluster is down ? I am looking for the high availability but it seems increasing number of data node would increase the probability of failure.

Please advise. Azhar