Message-
From: Russell Horn [mailto:[EMAIL PROTECTED]
Sent: Monday 02 February 2004 16:21
To: [EMAIL PROTECTED]
Subject: RE: Advise on High Availability configuration
Andrew Braithwaite wrote:
Each slave keeps a heartbeat to the master and in the event of a
failure, changes it's master
No, when we implemented high-availability MySQL servers we used MySQL's
inbuilt replication - this has been running here for years now and we have
had constant DB availability during that time, even though individual
machines have failed now and again. We're using 2 masters 4 slaves with
On Mon, Feb 02, 2004 at 09:17:08AM +0100, A.J.Millan wrote:
No, when we implemented high-availability MySQL servers we used MySQL's
inbuilt replication - this has been running here for years now and we have
had constant DB availability during that time, even though individual
machines have failed
.
Hope this helps with your study.
Cheers,
Andrew
-Original Message-
From: A.J.Millan [mailto:[EMAIL PROTECTED]
Sent: Monday 02 February 2004 08:17
To: [EMAIL PROTECTED]
Subject: Re: Advise on High Availability configuration
No, when we implemented high-availability MySQL servers we
Andrew Braithwaite wrote:
Each slave keeps a heartbeat to the master and in the event of a failure,
changes it's master to master2.
So how does this bit work? If one master falls over and slaves move to
master two, how do you rebuild master one without downtime? Don't the slaves
try and use
Hello All:
Thank you for all the advise provided on this issue.
Much appreciate Andrew's detailed answers and
alternate solution.
I will investigate the Replication method and try to
devise some strategy to make sure that the Slave
mirrors the Master as closely as possible. Also
taking
need dscussion, nicely
explained by Jeremy here:
http://jeremy.zawodny.com/blog/archives/000805.html
Cheers,
Andrew
-Original Message-
From: Russell Horn [mailto:[EMAIL PROTECTED]
Sent: Monday 02 February 2004 16:21
To: [EMAIL PROTECTED]
Subject: RE: Advise on High Availability
On Fri, Jan 30, 2004 at 10:36:34AM -0800, Gowtham Jayaram wrote:
CONFIGURATION:
[...]
- Additionally, I will setup a SCSII controller in
the Primary and Secondary Application machines so that
the actual data store (disk drive) runs on another
physical machine in a disk-array (RAID).
So
the same table simultaneously?
InnoDB has row level locking but MyISAM doesn't
Hope this helps,
Andrew
-Original Message-
From: Gowtham Jayaram [mailto:[EMAIL PROTECTED]
Sent: Friday 30 January 2004 18:37
To: [EMAIL PROTECTED]
Subject: Advise on High Availability configuration
Hello
Hello All;
I am in the process of examining a High Availability
(HA) configuration. The motivation is to not use
database replication (at least at this stage) because
of the need to work on the complete data set at any
given point in time. Here is the configuration choice
being considered
I am wary of something so 'do it yourself'. Have you looked at ReHat's
clustering solution?
http://www.redhat.com/software/rha/cluster/
http://www.redhat.com/software/rha/cluster/manager/
I don't think it has any issue with InnoDB, key buffers, etc.
I believe this solution works best for
11 matches
Mail list logo
