[SERVER-84238] Inconsistent Catalog access during aggregations Created: 15/Dec/23  Updated: 08/Jan/24  Resolved: 08/Jan/24

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

Type: Bug Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-84236 Forbid usage of CollectionCatalog::ge... Open
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22
Participants:
Linked BF Score: 115

 Description   

During aggregation creation we're accessing the Catalog with the inverse order of what it should be.

Instead of first acquiring a snapshot via AutoGet/Shard Acquisition that stashes the correct Catalog version we're:



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

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-84238 Force aggregations to use the stashed CollectionCatalog if possible (#17637)

GitOrigin-RevId: c767f8239d0d2905a06d1525c9b95c7aff5bd74f
Branch: master
https://github.com/mongodb/mongo/commit/f7c0000d16df3f38475f169c56a2c63e698e7890

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