[SERVER-49738] Consider removing minValid timestamp and term fields once enableMajorityReadConcern:false is removed Created: 20/Jul/20  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-34165 Remove rollback via refetch when it i... Closed
Assigned Teams:
Replication
Participants:

 Description   

Once rollbackViaRefetch is removed, which should be possible on enableMajorityReadConcern:false is removed, we should no longer have a need for the minValid optime. If we crash during secondary oplog application, we will always recover to a stable timestamp which was set at a timestamp where a complete batch had already finished, so we don't require it for crash resilience in this case. Similarly, recover to a timestamp always recovers to a consistent state post rollback, so we never go through a phase of inconsistency while waiting to reach a minValid timestamp.



 Comments   
Comment by William Schultz (Inactive) [ 20/Jul/20 ]

See related comment.

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