[SERVER-39226] Pause the Timestamp Monitor during rollback-to-stable Created: 28/Jan/19  Updated: 29/Oct/23  Resolved: 30/Jan/19

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

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to WT-4532 Fix null pointer access to WT_DATA_HA... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-01-28, Storage NYC 2019-02-11
Participants:
Linked BF Score: 71

 Description   

During rollback-to-stable the Timestamp Monitor is still running and calls into WiredTiger concurrently. While rollback-to-stable is running, no calls can be made into WiredTiger.

While rollback-to-stable is running, we should pause the Timestamp Monitor.



 Comments   
Comment by Githook User [ 30/Jan/19 ]

Author:

{'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek'}

Message: SERVER-39226 Pause the Timestamp Monitor during rollback-to-stable
Branch: master
https://github.com/mongodb/mongo/commit/09abfff1c4ad2f98a9b83093b7e8b6454bc7c393

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