|
But you only solve half of the problem - if your master goes down you can not
do write operations any more...
Still better than being down completely of course, especially if you have a
higher percentage of reads compared to writes, plus you
have the load-balancing if your reads are complex load-intensive queries.
Did you ever try master-master replication? Some people use that, but I think
it's not totally trivial, there are some potential
pitfalls.
MARK
> -----Original Message-----
> From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf
> Of Troy Hakala
> Sent: Tuesday, October 25, 2005 4:28 PM
> To: LinuxVirtualServer.org users mailing list.
> Subject: Re: Using LVS for MySQL traffic
>
>
> We're using master/slave replication. The LVS balances the
> reads from the slaves and the master isn't in the
> load-balancing pool at all. The app knows that writes go to
> the master and reads go the VIP for the slaves. Aside from
> replication latency, this works very reliably.
>
>
> On 10/25/05, mike <mike503@xxxxxxxxx> wrote:
> >
> > On 10/25/05, Troy Hakala <troy@xxxxxxxxxxxxxx> wrote:
> > > it works fine, we've been doing it for years. :-)
> > >
> >
> > thanks :)
> >
> > okay, here comes the next question then... just for curiosity - for
> > both of you guys.
> >
> > how are you replicating the data between mysql servers?
> >
> > NDB/MySQL clustering?
> > master/slave replication?
> > something else?
> >
> > thanks
> > - mike
> > _______________________________________________
> > LinuxVirtualServer.org mailing list -
> lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> >
> _______________________________________________
> LinuxVirtualServer.org mailing list -
> lvs-users@xxxxxxxxxxxxxxxxxxxxxx Send requests to
> lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
