[SERVER-43590] Add failpoint to disable oplog truncation Created: 24/Sep/19  Updated: 17/Oct/19  Resolved: 17/Oct/19

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

Type: New Feature Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Judah Schvimer
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Repl 2019-10-21
Participants:

 Description   

Our TLA+ specs assume the oplog is never truncated. This is a reasonable simplification and makes our specs closely resemble the abstractions in Raft, and it permits us to verify Raft's "Log Matching Property".

Introduce a failpoint to disable truncation. We will enable the failpoint in mongod in preparation for extracting an execution trace from mongod's log and checking it against our TLA+ specs.



 Comments   
Comment by Judah Schvimer [ 17/Oct/19 ]

Closing in favor of just using a really large oplog that we would never roll over.

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