Task #2491
Task #2490: ReplicationManagers on 3 CNs should only create one task per replica node
Evaluate ReplicationManager.createAndQueueTasks() for locking problems
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_replication
Target version:
Start date:
2012-03-15
Due date:
% Done:
100%
Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:
Description
Multiple MNReplicationTasks are being created for a single identifier and target replica node. Only one should be created. Review the locking code across the ReplicationManager instances to be sure that, although they all eventually get the lock, only one should create the task.
History
#1 Updated by Chris Jones about 12 years ago
- Status changed from New to Closed
ReplicationEventListener.entryAdded|Updated was queueing events and releasing the lock before the timeout on the other CNs (to do the same). I reduced the timouts to 10 ms, seeing that most queing took around 50 ms. This should keep only one CN queueing the event.
