[SERVER-36184] Delete the OplogStart stage Created: 18/Jul/18  Updated: 29/Oct/23  Resolved: 20/Jul/18

Status: Closed
Project: Core Server
Component/s: Querying, Storage
Affects Version/s: None
Fix Version/s: 4.1.2

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query 2018-07-30
Participants:

 Description   

This stage was used for optimizing predicates of the shape {ts: {$gte: <Timestamp>}} on the oplog. However, its implementation was MMAP-specific. On WiredTiger systems, the ts of each oplog entry forms the RecordId for the WT table backing the oplog. The beginning of the oplog scan can be found efficiently by simply seeking to the appropriate RecordId.

Since MMAP is no longer supported, OplogStart can be removed.



 Comments   
Comment by Githook User [ 20/Jul/18 ]

Author:

{'username': 'dstorch', 'name': 'David Storch', 'email': 'david.storch@10gen.com'}

Message: SERVER-36184 Remove RecordStore::getManyCursors().

This API was used by the parallelCollectionScan command and
by the OplogStart stage, both of which have been deleted as
part of removing support for MMAPv1.
Branch: master
https://github.com/mongodb/mongo/commit/cfcda44b4dde0b94f2ad592f7401711c9b3a20e2

Comment by Githook User [ 20/Jul/18 ]

Author:

{'username': 'dstorch', 'name': 'David Storch', 'email': 'david.storch@10gen.com'}

Message: SERVER-36184 Delete OplogStart stage.
Branch: master
https://github.com/mongodb/mongo/commit/eb0fa7a4aebb686ba0a1bf123cb96b09f8f51431

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