On Tue, 2009-09-29 at 00:16 +0200, John Feuerstein wrote:
> Eww, let me rephrase that:
>
> > So, let's suppose we have a sequential auto-incrementing column:
> > 1 11 21 31 41 51
> >
> > Now we fail-over to the secondary node and the column ends up
> > non-sequential:
> > 1 2 11 12 21 22 31 32 41 42 51 52 62 72 82
>
> The resulting column's keys are sequential, but the correct order of
> inserted messages can't be derived from this anymore.
Something you've missed is that the mysql will always increment. So it
wont insert like:
1 2 11 12 21 22 31 32 41 42 51 {switchover} 52 62 72 82
But like:
1 11 21 31 41 51 {switchover} 52 62 72 82 92 102 112...
It will only interleave if you have the two masters actively inserting
at the same time in a round-robin fashion. Failover using heartbeat or
ucarp will avoid this.
As long as your db's are in sync you wont get any problems. We've got a
similar setup and have had it change over a number of times with no ill
effects.
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
