[SERVER-53642] Cleanup writes to appliedThrough that changed as part of Lock Free Reads Created: 07/Jan/21  Updated: 06/Dec/22  Resolved: 22/Nov/21

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

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-58410 Discontinue writing to appliedThrough... Closed
Related
related to SERVER-59721 Node may become unable to sync from o... Closed
related to SERVER-53436 Transition to primary writes minValid... Closed
related to SERVER-61703 Complete TODO listed in SERVER-53642 Closed
Assigned Teams:
Replication
Participants:

 Description   

Lock-Free Reads and SERVER-53436 changed writes to appliedThrough that used to be with a Timestamp on lastApplied.

These writes are protected with the RSTL in X mode to ensure there are no readers. But with lock free reads that does no longer prevent readers from starting.

Doing this change was safe because without EMRC=false we don't need this document for recovery and a clean shutdown would be required for a downgrade.

However we should be able to clean up this more when the code for RMRC=false is removed.


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