Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: <19ee0b1be4bc84fb867fcf9e7b73a858@mail.gmail.com>
References: <f199e14b37b51afc2372fce59d7db096@mail.gmail.com>
	<CALoaWF4B3r5nJA=8OpR5cSUbqXpOJA13zFbXpWAw8Mj1jKt8Nw@mail.gmail.com>
	<19ee0b1be4bc84fb867fcf9e7b73a858@mail.gmail.com>
Date: Tue, 5 Nov 2013 13:50:37 -0800
Message-ID: 
 <CAKnq6PeC5BQuYO8xE4ackJ2qXyx=qGHc+T821v6VFKVGiibKeA@mail.gmail.com>
Subject: Re: Multi-master MySQL Setup
From: Patrick Miller <patrick.miller@sungard.com>
To: users@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=f46d04427108e5904804ea750545

--f46d04427108e5904804ea750545
Content-Type: text/plain; charset=ISO-8859-1

Take a look at the percona [1] implementation of mysql and there clustered
version.
Round robin reads and writes supported.

1] http://www.percona.com/

 Patrick


On Tue, Nov 5, 2013 at 9:55 AM, Adrian Lewis <adrian@alsiconsulting.co.uk>wrote:

> Hi Marty/Nux!,
>
> Thanks for the feedback - sounds like multi-master is not a good thing
> then! Load will likely be very small for at least the next 6 months but I
> figured that it was one of those things that could be set easily now
> (still setting up) that I might appreciate later.
>
> Based on both your responses, I think I'll just leave it well alone! Need
> to get to grips with pacemaker/corosync anyway for other reasons so I'll
> just try that with either DRBD replication or MySQL replication.
>
> Cheers,
>
> Adrian
>
> -----Original Message-----
> From: Marty Sweet [mailto:msweet.dev@gmail.com]
> Sent: 05 November 2013 17:23
> To: users@cloudstack.apache.org
> Subject: Re: Multi-master MySQL Setup
>
> Others may have had more success with this but from experience of MySQL in
> multi-master setups I would avoid this entirely.
>
> A common setup is using DRDB to provide a master/slave:
> Management 1 (MySQL Master) w/ virtual IP Management 2 (MySQL Slave)
>
> HA IP Address (for agents/services requiring DB write) which is assigned
> to the master (using Pacemaker).
>
> You can then send web management client to the HA IP Address as well.
>
> It may be worth considering if you need load balancing, depending on your
> setup - what loads are you experiencing?
>
> Marty
>
>
>
> On Tue, Nov 5, 2013 at 5:13 PM, Adrian Lewis
> <adrian@alsiconsulting.co.uk>wrote:
>
> > Hi All,
> >
> >
> >
> > Just wondering if anyone is using a MySQL multi-master configuration
> > with auto_increment_offset (e.g.10) and auto_increment_increment (1
> > for server 1, 2 for server 2 etc)? Does it work? Does anyone know a
> > reason why it doesn't or wouldn't work? Is there anything from an
> > application point of view that could/would trip up CS if
> > auto_increment values are set as more than 1?
> >
> >
> >
> > Not planning on deploying multimaster just yet but if I at least start
> > with an auto_increment of 10, I'd have the option of adding a second
> > master later and being able to load-balance more effectively.
> >
> >
> >
> > Thanks in advance,
> >
> >
> >
> > Adrian
> >
>
>

--f46d04427108e5904804ea750545--