[SERVER-46895] Do not check duplicate key violations on index builds during oplog application phase of initial sync Created: 16/Mar/20  Updated: 29/Oct/23  Resolved: 27/Mar/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2020-04-06
Participants:
Linked BF Score: 27

 Description   

A node is not consistent until initial sync is complete, which includes the oplog application phase.

This fatal assertion can fail during initial sync when inconsistencies are observed.



 Comments   
Comment by Githook User [ 02/Apr/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-46895 Do not check duplicate key violations on index builds during oplog application phase of initial sync

(cherry picked from commit 45db64dd0947fa13373a0ed03ce7c3da9d97f12b)
Branch: v4.4
https://github.com/mongodb/mongo/commit/e896d4dca291ba0ef3f9a63779c210780637336b

Comment by Githook User [ 27/Mar/20 ]

Author:

{'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}

Message: SERVER-46895 Do not check duplicate key violations on index builds during oplog application phase of initial sync
Branch: master
https://github.com/mongodb/mongo/commit/45db64dd0947fa13373a0ed03ce7c3da9d97f12b

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