search

zkfan / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

Slave replicator loses track of position after a process restart #109

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Slave replicators appear to lose track of their positions when the replicator 
process is restarted under load. 

To reproduce: 

1. Set up master/slave replication.

2. Add a load constant small transactions on the master.  The transactions 
should insert new records with unique primary keys. 

3. Restart the slave process using 'replicator restart'. 

The slave will fail with the following error in its logs:   
org.drizzle.jdbc.internal.common.QueryException: Duplicate entry '533' for key 
'PRIMARY'

This is a very repeatable bug and appears to be a regresion

Original issue reported on code.google.com by berkeley...@gmail.com on 12 Jun 2011 at 3:08

GoogleCodeExporter commented 9 years ago 
This appears to be the same parallel replication bug that was fixed in Issue 
180.  As of the fixes to parallel queues it is not reproducible.

Original comment by berkeley...@gmail.com on 10 Aug 2011 at 7:17

GoogleCodeExporter commented 9 years ago

Original comment by berkeley...@gmail.com on 10 Aug 2011 at 7:17