Le Thursday 22 May 2008 10:40:46, vous avez écrit :
Maybe, you search the zope-dev archive to find the thread that convinced
us to change the former behaviour (the one you want now again)
into the current one?
Adding links for possible future reference:
We have put up two boxes in a MySQL master-master replication setup
[1]. As long as we only write to one of the masters all is fine.
Writing to both masters (and expecting MySQL to sort it out) is giving
us trouble. We see things like:
Last_Errno: 1062
Last_Error: Error 'Duplicate entry
Hi Russ,
This is correct. I should have mentioned that the two servers are
configured so that server A creates odd, server B even sequence
numbers. This makes the duplicate id error pretty mysterious, IMO ;-)
Stefan
On 22.05.2008, at 13:15, Russ Ferriday wrote:
I have not read the
Stefan H. Holek wrote:
We have put up two boxes in a MySQL master-master replication setup
[1]. As long as we only write to one of the masters all is fine.
Writing to both masters (and expecting MySQL to sort it out) is giving
us trouble. We see things like:
Last_Errno: 1062
Last_Error:
Hi,
Shane Hathaway wrote:
Stefan H. Holek wrote:
We have put up two boxes in a MySQL master-master replication setup
[1]. As long as we only write to one of the masters all is fine.
Writing to both masters (and expecting MySQL to sort it out) is
giving us trouble. We see things like: