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:
Let me rephrase this. Would it be ok to change *all* tables to use the
InnoDB engine (except new_oid)?
Stefan
On 19.05.2008, at 10:55, Stefan H. Holek wrote:
I am playing with database replication (MySQL) and have found the
following caveats:
- don't mix engine types (MyISAM,
I am playing with database replication (MySQL) and have found the
following caveats:
- don't mix engine types (MyISAM, InnoDB)
- don't use temporary tables
Now, RelStorage does both and so I was wondering how to proceed with
replication. Would it be prudent to assume that
Stefan H. Holek wrote:
I am playing with database replication (MySQL) and have found the
following caveats:
- don't mix engine types (MyISAM, InnoDB)
- don't use temporary tables
Now, RelStorage does both and so I was wondering how to proceed with
replication. Would it be prudent to
