[SERVER-74200] Implement the 2-phase oplog notification in CreateCollectionCoordinator Created: 21/Feb/23  Updated: 29/Oct/23  Resolved: 22/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-74248 Adapt the aggregation pipeline suppor... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
Participants:

 Description   

shardCollection is currently generating an op entry just after committing its metadata into the sharding catalog - and in order to guarantee at-least-once-delivery semantics, also in case of early exits after a stepdown event (1, 2).

Nevertheless, the current properties of the DDL do not guarantee that the timestamp of the op entry will always predate the time of the first user write within the sharded collection.

To overcome these inaccuracies, the commit may be described on the oplog through a 2-phase protocol.



 Comments   
Comment by Githook User [ 21/Mar/23 ]

Author:

{'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-74200 Implement the 2-phase oplog notification in CreateCollectionCoordinator
Branch: master
https://github.com/mongodb/mongo/commit/521b53af47740717ac61a6df38ec2f17eba26c2c

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