[SERVER-27616] Fix $lookup/$graphLookup foreign collection sharding check race condition Created: 09/Jan/17  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: 3.5.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James Wahlin Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 1
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-27308 Reduce cost of sharding check in Docu... Closed
is related to SERVER-39015 Make local reads for $lookup/$graphLo... Closed
Assigned Teams:
Query Execution
Operating System: ALL
Participants:

 Description   

$lookup (and $graphLookup on resolution of SERVER-27308) perform a check to confirm that the foreign collection is not sharded, prior to each foreign collection query. This check is done within a lock that is released prior to query execution, introducing a potential race condition where the foreign collection could be sharded before the query is executed.



 Comments   
Comment by David Storch [ 02/Aug/19 ]

SERVER-39015 proposes a fix for this problem.

Generated at Thu Feb 08 04:15:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.