[SERVER-21862] Use record store directly to read from oplog for replication Created: 11/Dec/15  Updated: 06/Dec/22  Resolved: 09/Nov/20

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

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-24661 Secondary block reader a very long ti... Closed
is related to SERVER-5729 Special-case concurrency model for op... Closed
is related to SERVER-20328 Allow secondary reads while applying ... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

By using the record store directly we can avoid any locking issues and use a snapshot to return data at any time.

We must be careful of operations which drop/recreate the oplog, like resync/compact/etc, since the record store pointer will have to be re-acquired once it becomes invalid.



 Comments   
Comment by Spencer Brody (Inactive) [ 06/Oct/17 ]

This seems related to SERVER-20328

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