We're running bi-directional replication between two servers running MySQL 3.23.56.
One server being active the other a hot standby.
Wanting to switch to the hot standby I noticed that replication had
ceased on the HS server. The show slave status:
| 192.168.1.10 | mysql_replicator | 3309 | 60 |
hostname-bin.075 | 1159 | No
| | | 1062 | error
'Duplicate entry '11609031'
for key 1' on query 'insert into CLOCK_INSTALL (URL, MACHINE_ID,
INSTALL_TIME,REMOTE_IP,LASTURL) values
('FRZE1002','81E7A3FBE4A64E6A8CDE92EB00B4D8B0',Now(),'127.0.0.1','')' |
0 |
The install_id('11609031') for the table is of auto_increment and that
id is already present in the HS server.
The previous entry '11609030' is the same accross the servers. How
could this happen and why doesn't mysql just increment to '11609032' for
this insert?
The replication has not been touched for weeks and it was working
properly when it was set up. The HS was never in an active situation so
corruption is ruled out on its end.
I'd like to solve this without downtime to the primary server.
Any help would be appreciated.
Thanks
Chris
--
Christopher Ferry <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
