[SERVER-63694] Accommodate WT-8170 Created: 15/Feb/22  Updated: 29/Oct/23  Resolved: 17/Feb/22

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

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

Issue Links:
Backports
Depends
is depended on by WT-8170 Reduce complexity of timestamp usage ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.3
Sprint: Execution Team 2022-02-21
Participants:

 Description   

WT-8170 (broadly) aims to improve the WT timestamp assertions. This ticket is to make the accompanying changes for MDB. We'll the following changes:

  • Apply the mixed_mode assertion to the following tables that currently have no assertions:
    • internal-
    • oplog (obsoleted as WT no longer saves TS information on logged tables and therefore disables assertions)
    • config.system.indexBuilds (record store and indexes)

We expect to move config.system.indexBuilds (in addition to the _mdb_catalog, which currently has an out of timestamp order write and no assertions today) to ordered. See SERVER-60753 and SERVER-60754.

Ideally this patch can go in without causing any testing failures such that WT-8170 can be dropped at a later time. If that's not viable, we will coordinate a dance of:

  • Disable assertions in a patch
  • Drop WT-8170
  • Re-enable assertions


 Comments   
Comment by Githook User [ 17/Feb/22 ]

Author:

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

Message: SERVER-63694: Recategorize WT timestamp assertions.

Correct unittests to abide the ordered assertion.
Branch: master
https://github.com/mongodb/mongo/commit/332b40e48e404d4d358119e199ef2c4c634a7c58

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