On Wed, Oct 20, 2010 at 1:37 AM, Walter Heck - OlinData.com <
li...@olindata.com> wrote:
> To Clarify this a bit: You can only reliably do writes to one server.
>
Also not *entirely* true: nothing prevents you from using the two masters
for distinct databases - or even tables - and just having th
To Clarify this a bit: You can only reliably do writes to one server.
Your reads can go to both servers with no problems.
For reads that need to read data that was just written though, you
need to read from the 'active' master, as you can not rely on
replication to be instantaneous.
On Tue, Oct 19
On Tue, Oct 19, 2010 at 1:03 PM, Carl wrote:
> Johan,
>
> You state that master - master is not reliable in dual active environments.
> I am in the process of setting up just such an environment (moderate active
> on the primary server, lighter activity on the other server.) Do you know
> where
,
Carl
- Original Message -
From: "Johan De Meersman"
To: "short cutter"
Cc: "Brent Clark" ;
Sent: Tuesday, October 19, 2010 5:10 AM
Subject: Re: Master Master Replication ... do a fail over and a week agos
data is revealed.
On Tue, Oct 19, 2010 a
On Tue, Oct 19, 2010 at 9:48 AM, short cutter wrote:
> 2010/10/18 Brent Clark :
> > Hiya
> >
> > I run MySQL Master - Master Replication. Ive had an interesting situation
> > whereby I failed over using heartbeat but whats is interesting is that
> via
> > the application (vbulletin), I see that
2010/10/18 Brent Clark :
> Hiya
>
> I run MySQL Master - Master Replication. Ive had an interesting situation
> whereby I failed over using heartbeat but whats is interesting is that via
> the application (vbulletin), I see that the forums was showing that a weeks
> ago data.
>
Why using M-M repl
Hiya
I run MySQL Master - Master Replication. Ive had an interesting
situation whereby I failed over using heartbeat but whats is
interesting is that via the application (vbulletin), I see that the
forums was showing that a weeks ago data.
I had to re fail over to the original server and th
