[SERVER-1086] dropdups may drop different dups on slave Created: 04/May/10  Updated: 12/Jul/16  Resolved: 28/Jul/11

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 1.9.2

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-3643 dropdups replication corner cases Closed
is related to SERVER-6957 Replication Issues with Indexes Closed
Participants:

 Description   

I believe that when we build an index in drop dups mode, different dups may be dropped on slave than on master as a result of different natural ordering on the slave.



 Comments   
Comment by auto [ 28/Jul/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: make sure to drop the same dups on master and secondaries SERVER-1086
Branch: master
https://github.com/mongodb/mongo/commit/724fc134c4a9855b66a8c6f594a354ea888f60a8

Comment by Dwight Merriman [ 20/Jul/11 ]

i guess we can just drop the one with the lower _id

Comment by Dwight Merriman [ 20/Jul/11 ]

if this is not in 2.0 dropDups may have to be disabled.

Comment by Eliot Horowitz (Inactive) [ 19/Apr/11 ]

We should just logOp the deletes

Generated at Thu Feb 08 02:56:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.