[SERVER-46297] Make all primary durable timestamp updates go through the JournalListener Created: 21/Feb/20  Updated: 29/Oct/23  Resolved: 21/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
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-44555 Implement replicate before journaling Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-02-24
Participants:
Linked BF Score: 0

 Description   

waitForWriteConcern is sometimes setting the last durable timestamp manually, as well as implicitly by calling into the storage engine for durability.

These should be consolidated for ease of understanding, because the current state is confusing; and must be done in order to pick up the correct timestamp in getToken for setting the durable timestamp.



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

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-46297 make all primary durable timestamp updates go through the journal listener
Branch: master
https://github.com/mongodb/mongo/commit/b03fb82e1737b28fbd322e9bf200bb7a3176d9f7

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