[SERVER-64760] Correctly timestamp catalog writes for index recovery when an oplog entry timestamp is present Created: 21/Mar/22  Updated: 29/Oct/23  Resolved: 23/Sep/22

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

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

Issue Links:
Depends
is depended on by SERVER-60753 Removing index build entries from 'co... Closed
Issue split
split to SERVER-69877 Remove untimestamped writes to the ca... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2022-10-03
Participants:

 Description   

We use canAcceptWritesFor to determine if we're a primary which among other things, controls whether we should timestamp writing to the catalog. There are cases where we are writing to the catalog with a perfectly valid timestamp from an oplog entry, but we omit passing the timestamp to the transaction.



 Comments   
Comment by Githook User [ 23/Sep/22 ]

Author:

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

Message: SERVER-64760 Correctly timestamp catalog writes for index recovery when an oplog entry timestamp is present
Branch: master
https://github.com/mongodb/mongo/commit/cd39149861aeea410f4b1f3018adcb780aa340b6

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