Closed Bug 607878 Opened 14 years ago Closed 14 years ago

Replication keeps dying with a duplicate key error / REPLACE isn't replication-safe in MySQL 5.0

Categories

(Webtools :: Bouncer, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: justdave, Assigned: justdave)

Details

Attachments

(1 file)

Geting this error every day or two on the backup replicator server:

Error 'Duplicate entry '2491293875' for key 1' on query. Default database: 'bouncer'. Query: 'REPLACE mirror_location_mirror_map SET location_id='1700',mirror_id='318',active='0''

It looks like REPLACE isn't exactly replication safe in MySQL 5.0.

Details at http://bugs.mysql.com/bug.php?id=53194

We can replace the query in question (which is in the sentry code) with an INSERT ... ON DUPLICATE KEY UPDATE query, which is replication safe.

Docs on that are at
http://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html
Attached patch patchSplinter Review
Sending        sentry/sentry.pl
Transmitting file data .
Committed revision 76416.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
I can pull this into github: http://github.com/fwenzel/tuxedo/commit/e639bdb

Perhaps I should give you access so you can push such changes to the main code repository directly?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: