[SERVER-83611] Do not obtain CRI multiple times in cluster aggregate path Created: 27/Nov/23  Updated: 28/Nov/23  Resolved: 28/Nov/23

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

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

Issue Links:
Backports
Depends
Related
related to SERVER-83614 $queue/$lookup pipeline can throw if ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2
Sprint: QE 2023-12-11
Participants:
Linked BF Score: 154

 Description   

For bonus points, downgrade the invariant around cri in 'getTargetedShards' to a tassert 



 Comments   
Comment by Githook User [ 28/Nov/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-83611 Acquire CRI in dispatchShardPipeline if none is present

(cherry picked from commit 7fa5d2bbdf4895b3f5863531a947a8fab1b08190)
Branch: v7.2
https://github.com/mongodb/mongo/commit/05a36cbeb1a53962e3abfb5008078f6314caed17

Comment by Githook User [ 28/Nov/23 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com', 'username': 'mtandrei'}

Message: SERVER-83611 Acquire CRI in dispatchShardPipeline if none is present
Branch: master
https://github.com/mongodb/mongo/commit/7fa5d2bbdf4895b3f5863531a947a8fab1b08190

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