Thanks for the feedback everyone. I was looking into using the replication
to do point in time recovery to protect against some stability issues I was
seeing with my 4.x setup where the ndb nodes seem to have occasional
problems in recovering from power outages or general server shutdowns.
Oftentimes one node would start but the other wouldn't or they would only
start one at a time or I'd have to resort to re-initializing the data nodes
I guess the way to go is to upgrade my server to take advantage of all the
good work you guys are doing.
From: Simon Garner [mailto:sgarner@stripped]
Sent: June 30, 2006 3:09 AM
To: Stewart Smith
Subject: Re: cluster replication in 4.1.16
Stewart Smith wrote:
> On Fri, 2006-06-30 at 17:49 +1200, Simon Garner wrote:
>> The problem with this is there's no way to use it in conjunction with
>> binary logs for "always current" or point in time backup and recovery.
>> Recovering from an ndb backup only gets you back to whatever point in
>> time the backup was taken.
>> It would be great if MySQL Cluster had some functionality for
>> centralised binary logging (e.g. on the management node). Then one could
>> do a cluster backup (which would record the current binary log position)
>> and then recover from there by re-applying queries using the binlogs. I
>> don't know if that's technically feasible...
> it is, it's in 5.1. MySQL Cluster Replication will produce a single,
> canonical binlog for the cluster. I go over the architecture in my
> Cluster talk that's on Google Video.
Oh! Nice work. :)
Looks like 5.1 is going to be a big step forward!
MySQL Cluster Mailing List
For list archives: http://lists.mysql.com/cluster
To unsubscribe: http://lists.mysql.com/cluster?unsub=1