[SERVER-38425] Oplog Visibility Query is a collection scan in 3.2.21 Created: 05/Dec/18  Updated: 29/Oct/23  Resolved: 17/Dec/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.21
Fix Version/s: 3.2.22

Type: Bug Priority: Major - P3
Reporter: Eric Sedor Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: SWCW, SWNA
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-37468 Problem with initial sync when adding... Closed
Problem/Incident
is caused by SERVER-30724 Initial sync might miss ops that were... Closed
Related
Operating System: ALL
Sprint: Repl 2019-01-14
Participants:

 Description   

The oplog visibility query introduced to 3.2.21 in SERVER-30724 does not use the OplogReplay query flag. This causes initial sync failures on any sufficiently large oplog, because the query uses a collection scan from the beginning of the oplog collection.



 Comments   
Comment by Githook User [ 17/Dec/18 ]

Author:

{'username': 'ajdavis', 'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis'}

Message: SERVER-38425 Use oplogReplay for oplog visibility query
Branch: v3.2
https://github.com/mongodb/mongo/commit/105acca0d443f9a47c1a5bd608fd7133840a58dd

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