[SERVER-44359] Race between oplog visibility thread and timestamped inserts in dbtest repl Created: 01/Nov/19  Updated: 29/Oct/23  Resolved: 02/Nov/19

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

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

Issue Links:
Depends
Duplicate
is duplicated by SERVER-44196 Complete TODO listed in SERVER-43399 Closed
Related
related to SERVER-42497 Detect/log unintentional untimestampe... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-11-04
Participants:
Linked BF Score: 0

 Description   

There was a race between the background WTOplogJournalThread and the test running inserts. The inserts set the WT transaction timestamp to Timestamp(1, 1) and that was why query_timestamp returned Timestamp(1, 0). SERVER-42497 added the setTimestamp call to the inserts.

In production we don't have any logic that sets timestamps to anything other than what the LogicalClock timestamp generator gives us, so this race cannot occur in production. Ideally, no dbtest would explicitly set the timestamps backwards like this.



 Comments   
Comment by Githook User [ 02/Nov/19 ]

Author:

{'name': 'Lingzhi Deng', 'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-44359: Fix race between oplog visibility thread and timestamped inserts in dbtest repl
Branch: master
https://github.com/mongodb/mongo/commit/1514bfc14ba56a7d991dea02f4af9b0137b4444e

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