[SERVER-35805] Maintain checkpoint thread timestamp information for the inMemory storage engine and thereby support recoverable rollback with inMemory Created: 26/Jun/18  Updated: 29/Oct/23  Resolved: 27/Jul/18

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on WT-4178 Fixes for wt_btree_immediately_durabl... Closed
depends on WT-4174 Do not access the lookaside file in r... Closed
Duplicate
is duplicated by SERVER-36022 Turn on recoverable rollback testing ... Closed
Gantt Dependency
has to be done before SERVER-36101 Replication should not depend on the ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-07-02, Storage NYC 2018-07-16, Storage NYC 2018-07-30
Participants:

 Description   

Recoverable rollback doesn't work with the inMemory WT storage engine because critical timestamp information is maintained in the WiredTigerCheckPointThread that the inMemory engine does not run.

This task is to maintain that timestamp information for the inMemory engine, check that recoverable rollback testing works with the inMemory engine, and enable said testing.



 Comments   
Comment by Githook User [ 27/Jul/18 ]

Author:

{'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-35805 Support recoverable rollback with the inMemory WT storage engine

Includes disabling the 'enableInMemoryTransactions' server parameter
Branch: master
https://github.com/mongodb/mongo/commit/8f5ece1607915694a3a7392f0042ed0a3c7e57f2

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