[SERVER-76923] Allow bypassing checks for un-timestamped writes as standalone Created: 08/May/23  Updated: 29/Oct/23  Resolved: 10/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: 7.0-release-blocker
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-76924 Disable WT timestamp order checks whe... Closed
Problem/Incident
causes SERVER-77019 Initialize service context in wiredti... Closed
Related
related to SERVER-77533 Change default value of allowUnsafeUn... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Execution Team 2023-05-15
Participants:

 Description   

We have started disallowing un-timestamped writes to timestamped tables, as doing these is not necessarily safe. However, there are exceptional situations, including some restore-from-backup scenarios, where such writes are safe and necessary.



 Comments   
Comment by Githook User [ 10/May/23 ]

Author:

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

Message: SERVER-76923 Allow bypassing checks for untimestamped writes as standalone

(cherry picked from commit 21a479cd5b0cf16449eeaa31781397c8cc838a41)
Branch: v7.0
https://github.com/mongodb/mongo/commit/2474f0cec72acc0248b019b10052d484e69c6e5b

Comment by Githook User [ 10/May/23 ]

Author:

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

Message: SERVER-76923 Allow bypassing checks for untimestamped writes as standalone
Branch: master
https://github.com/mongodb/mongo/commit/21a479cd5b0cf16449eeaa31781397c8cc838a41

Comment by Geert Bosch [ 09/May/23 ]

It would be good if we still could log the error. Also, we'll need to straighten out whether we can make the suppression optional with a --allow-unsafe-untimestamped-writes option, or similar.

Comment by Gregory Wlodarek [ 09/May/23 ]

Thanks monica.ng@mongodb.com. That is the config option I'm planning on using to resolve this.

Comment by Monica Ng [ 09/May/23 ]

FYI, gregory.wlodarek@mongodb.com I'm not sure if the server team is aware but there is a configuration option no_timestamp in WiredTiger's begin_transaction method which will permit updates without a timestamp to occur after a key has already been updated using a timestamp.

Generated at Thu Feb 08 06:34:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.