[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: This API was used by the parallelCollectionScan command and |
| Comment by Githook User [ 20/Jul/18 ] |
|
Author: {'username': 'dstorch', 'name': 'David Storch', 'email': 'david.storch@10gen.com'}Message: |