[SERVER-77679] Untimestamped write assertion hit when running with recoverFromOplogAsStandalone=true Created: 01/Jun/23 Updated: 29/Oct/23 Resolved: 16/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.0
|
||||
| Sprint: | Execution NAMR Team 2023-06-26 | ||||
| Participants: | |||||
| Description |
|
max.hirschhorn@mongodb.com was inspecting a build failure and tried to launch mongod with --setParameter recoverFromOplogAsStandalone=true, and ran into the following error:
This is a background thread doing untimestamped writes on the config.transactions collection. Even though allowUnsafeUntimestampedWrites=true was used, the error still fired because we assumed there would be no untimestamped writes when running with recoverFromOplogAsStandalone=true, but that's not true. |
| Comments |
| Comment by Githook User [ 21/Jun/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 5c9e6404becc564d16857a869a5b5cb2e2bb0f1d) |
| Comment by Githook User [ 16/Jun/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |