[DRBD-user] mysql on drdb or mysql replication

paddy paddy at panici.net
Fri Feb 10 18:22:13 CET 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Fri, Feb 10, 2006 at 11:22:14AM -0600, Nate Reed wrote:
> On Friday 10 February 2006 11:06, Luc de Louw wrote:
> > Nate Reed wrote:
> > > On Friday 10 February 2006 10:51, Pierre Ancelot wrote:
> > >> Don't do this, you will corrupt your database.
> > >> mysql deals with the database in memory of each node
> > >>
> > >> Meaning if you do this,
> > >>
> > >> every node will load database from the files
> > >> each node will modify the database in memory.
> > >
> > > This is not a problem if you only have one active node since you would
> > > only run mysql on the active.
> >
> > Running a MySQL Cluster on a single node makes no sense for me. The
> > complexity of MySQL Clusters to set up and maintain is not worth the few
> > seconds you win when switching the active node.
> >
> > Eighter run it on DRBD (Proved working and stable) or test it with
> > MySQL-Cluster.
> 
> I must have lost track of the discussion.  :)  I didn't suggest running MySql 
> Cluster on a single node.  Clearly, one has to choose between 1) MySql 
> clustering on multiple nodes and 2) using DRBD active/passive with mysql 
> running on a single node.  Not both.

and IIRC MySQL-Cluster has to keep the whole database in RAM ?

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall



More information about the drbd-user mailing list