[SERVER-84273] Wrong description of all_durable timestamp in repl architecture guide Created: 13/Dec/23  Updated: 12/Jan/24  Resolved: 12/Jan/24

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

Type: Bug Priority: Minor - P4
Reporter: Daotang Yang Assignee: Moustafa Maher
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-12-25, Repl 2024-01-08, Repl 2024-01-22
Participants:

 Description   

all_durable: All transactions with timestamps earlier than the all_durable timestamp are committed. This is the point at which the oplog has no gaps, which are created when we reserve timestamps before executing the associated write. Since this timestamp is used to maintain the oplog visibility point, it is important that all operations up to and including this timestamp are committed and durable on disk. This is so that we can replicate the oplog without any gaps. 

The "and durable on disk" should be removed.

URL: https://docs.devprod.prod.corp.mongodb.com/mongo/src/mongo/db/repl/



 Comments   
Comment by Githook User [ 12/Jan/24 ]

Author:

{'name': 'Moustafa Maher', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}

Message: SERVER-84273 Wrong description of all_durable timestamp in repl architecture guide (#17840)

GitOrigin-RevId: d20ac5bce0474a29fc97ff2f113b1c7157931cc5
Branch: master
https://github.com/mongodb/mongo/commit/db5dc513c1d7cee8c929a438429265292e335e8c

Comment by Matthew Lewandowski [ 18/Dec/23 ]

daotang.yang@mongodb.com Heads up, the Pine Documentation actually pulls from the github markdown documentation, so the change can be made directly there.

Comment by David Hou [ 14/Dec/23 ]

Moving from DOCSP to DEVPROD as this does not deal with external documentation.

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