Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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. > Let's say a first node write down it's changes in files > The next node won't be aware of those changes and will write down it's > own changes. > > Result, the changes of the first node will be erased. > > > > Other case, if you are in a load-balanced environnement, the user enters > some data on a node but next node is unaware of those changes.... > > use mysql-cluster, it's easy to implement (advice, use at least mysql 5) > http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers. >html check this > > See you :) > Pierre. > > On Fri, 2006-02-10 at 08:51 +0100, Peter Müller wrote: > > Thank you all for your useful answers. I have drbd already running so I > > guess I will try using it. > > > > > ----- Original Message ----- > > > From: "Nate Reed" <nreed at awarix.com> > > > > > > Am I correct that mysql replication would allow multiple active nodes > > > while drbd limits you to a basic active/passive configuration? > > > > Yes, you are correct. You just need to configure replication on both > > nodes.