On 10/9/07, Lloyd Kvam <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-10-09 at 14:12 -0400, Flaherty, Patrick wrote:
> > > What about multimaster replication?
> > Multi Master made me feel a bit icky. Auto-increment offsets the same
> > logshipping stuff others have had problems with.
> A MySQL slave
On Tue, 2007-10-09 at 10:43 -0400, Flaherty, Patrick wrote:
> I'm planning to set up an HA mysql cluster.
Oddly enough, I just got an email from mysql.com advertising high
availability training in Burlington, MA later this month. Let me know
if you want a copy of the email.
--
Lloyd Kvam
Venix
On Tue, 2007-10-09 at 14:12 -0400, Flaherty, Patrick wrote:
> > What about multimaster replication?
>
> Multi Master made me feel a bit icky. Auto-increment offsets the same
> logshipping stuff others have had problems with.
A MySQL slave has a single master. A master can have multiple slaves
On Tue, 2007-10-09 at 10:43 -0400, Flaherty, Patrick wrote:
> Replication - One master server accepts writes, on write ships it's
> logs to the slave server(s). Async may not be a problem, but seems
> silly there's no flag to wait for the slaves to report a write was
> successful.
Replication is
> What about multimaster replication?
Multi Master made me feel a bit icky. Auto-increment offsets the same
logshipping stuff others have had problems with. There are also other
"implementations" of mmr, but they are just sets of scripts that mimic
heartbeat. In the end, it's the same as normal
On 10/9/07, Flaherty, Patrick <[EMAIL PROTECTED]> wrote:
> I'm planning to set up an HA mysql cluster. The database serves as a
> backend to a set of webservers (HW loadbalanced). The DB has light load,
> but when it breaks the site breaks, so I can't really get away with it
> as a single point of
On 10/09/2007 10:43 AM, Flaherty, Patrick wrote:
> I'm planning to set up an HA mysql cluster. The database serves as a
> backend to a set of webservers (HW loadbalanced). The DB has light load,
> but when it breaks the site breaks, so I can't really get away with it
> as a single point of failure.
On Tuesday 09 October 2007 10:43, Flaherty, Patrick wrote:
> I think I've settled on the DRBD method. Using a network block device
> and failing back and forth using heartbeat and a floating ip, though log
> shipping seems pretty straightforward.
>
> Does anyone have any positive or negative feedba