8 messages in com.mysql.lists.clusterRe: MySql Cluster 5.0
FromSent OnAttachments
Sandeep Bhoyar06 Aug 2007 03:16 
Gaël Marmillod06 Aug 2007 04:16 
Liang Chen07 Aug 2007 23:35 
Brian Moon07 Aug 2007 23:44 
Bond Masuda08 Aug 2007 00:04 
B. Keith Murphy09 Oct 2007 23:01 
Jason Snell10 Oct 2007 08:11 
Stewart Smith14 Oct 2007 23:05 
Subject:Re: MySql Cluster 5.0
From:Stewart Smith (stew@mysql.com)
Date:10/14/2007 11:05:13 PM
List:com.mysql.lists.cluster

On Wed, 2007-10-10 at 02:01 -0400, B. Keith Murphy wrote:

I have set up a devel/staging cluster in vmware. It isn't perfect, but it does work. I had heartbeat issues from the start because of I/O contention. What I did to resolve the problem was move one of the VMs to another VM server. The problem was that both nodes were writing to disk at the same time when checkpointing. Since we didn't have a massive disk subsystem this caused the problems. Moving the VM to another server alleviated the simultaneous writes to the same disk. The nodes haven't missed a heartbeat check since. You might not have two VMWare servers so this might not be an option. Unfortunately, the only heartbeat configuration variable I know of just determines how often the heartbeat checks are performed. Doesn't help this issue at all.

All this being said, I would never ever consider building a production cluster on VMs. Consider yourself warned :)

You can also limit the rate at which checkpointing occurs. This means that more REDO log may be needed though (for changes that happen during/between checkpoints)

Jumpstart your cluster: http://www.mysql.com/consulting/packaged/cluster.html