[SERVER-3968] replica set sync halts on dup key when using upserts on a collection with a unique index Created: 28/Sep/11  Updated: 30/Mar/12  Resolved: 30/Sep/11

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.0.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Pascal Masschelier Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux 64bit


Operating System: ALL
Participants:

 Description   

In a replica-set with 2 data nodes an one arbiter
I do upserts in a collection having a unique index on a field
all works as expected on primary, 2nd upsert on same index value replaces the first one. But rs.status() reports dup key on secondary.

doing a full resync of secondary did'nt help: error reappears with next upsert.

As a workaround, I added remove before upsert and have no longer sync errors.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 30/Sep/11 ]

Ok - let us know if you see it again.

Comment by Pascal Masschelier [ 28/Sep/11 ]

I didn't manage to reproduce the issue on a test replica set. The bug is probably in my brain. sorry. you can close.

Comment by Scott Hernandez (Inactive) [ 28/Sep/11 ]

Can you please post a script which reproduces these steps?

Generated at Thu Feb 08 03:04:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.