[SERVER-33270] Poke the WTCheckpoint thread to run when the first stable checkpoint becomes available. Created: 12/Feb/18  Updated: 29/Oct/23  Resolved: 16/Feb/18

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

Type: Task Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: rollback-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-02-26
Participants:

 Description   

In 3.6 all writes to WT tables are journaled. Thus if a node crashes coming out of initial sync, WT recovery will put the data into its correct post-initial sync state.

However, the recoverable rollback project removes journaling from some tables. This introduces a window where a node that crashes and restarts may not recognize it had completed initial sync. Specifically, this crash window is after a node comes out of initial sync, but before its first checkpoint is taken.

By default, WT checkpoints every 60 seconds. This ticket is for notifying the checkpoint thread right when replication communicates a stable timestamp is available that is >= the initial sync timestamp. This change will not guarantee that seeing a node report as a secondary implies it is resilient to a crash requiring a resync.



 Comments   
Comment by Githook User [ 16/Feb/18 ]

Author:

{'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}

Message: SERVER-33270: Trigger a first checkpoint when the initial sync time becomes stable.
Branch: master
https://github.com/mongodb/mongo/commit/0342dc52a3f48988038baf76d000a3fc8340cf2e

Generated at Thu Feb 08 04:32:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.