[SERVER-4474] Initial sync should ignore capped collection dup key error, too Created: 12/Dec/11  Updated: 11/Jul/16  Resolved: 20/Dec/11

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.0.3, 2.1.0

Type: Bug Priority: Major - P3
Reporter: Kristina Chodorow (Inactive) Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

12582 duplicate key insert for unique index of capped collection



 Comments   
Comment by auto [ 22/Dec/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Ignore capped dup key error on initial sync SERVER-4474
Branch: v2.0
https://github.com/mongodb/mongo/commit/45190b81b571d7cc4eaa0b527d8e120e45672612

Comment by auto [ 20/Dec/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Ignore capped dup key error on initial sync SERVER-4474
Branch: master
https://github.com/mongodb/mongo/commit/5d241544ff2ad9a6d93c8fe2eb665972a9b69cb0

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