[SERVER-71957] Trigger Collection instantiation in multi-document transaction read path when needed Created: 08/Dec/22  Updated: 29/Oct/23  Resolved: 09/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Henrik Edin
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-72608 Use minValid instead of minVisible wh... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-12-26, Execution Team 2023-01-09, Execution Team 2023-01-23
Participants:
Linked BF Score: 158

 Description   

We need to call openCollection for read operations in multi-document transaction read path when read timestamp is less than latest DDL operation



 Comments   
Comment by Githook User [ 09/Jan/23 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-71957 Fix banned_collection_reads_in_txn.js
Branch: master
https://github.com/mongodb/mongo/commit/1d1514b2aa235695f1b7649db620f986e16c6690

Comment by Githook User [ 09/Jan/23 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-71957 Integrate point-in-time catalog lookups into locked read setup path

A new version of AutoGetCollectionForRead was added when the PIT catalog lookup feature flag is enabled but we are not in the lock-free read code path.

The new AutoGetCollectionForReadPITCatalog does not need to retry acquiring locks when a DDL operation happens between opening the storage snapshot and taking the collection level locks. Instead, when this case is detected we instantiate a Collection instance that matches with the opened storage snapshot.

Moved some shared code to the 'catalog_helper' namespace.
Branch: master
https://github.com/mongodb/mongo/commit/b36a39531c1506de6d989b8844ce2620081c2312

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