[SERVER-60384] Fix race in graphLookup execution test Created: 01/Oct/21  Updated: 29/Oct/23  Resolved: 04/Oct/21

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

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 145

 Description   

This test in lookup_unionWith_subpipeline_local_read.js assumes that the primary shard will execute a subpipeline of the $graphLookup first. But if the non-primary shard executes a subpipeline first, it targets the primary which must do a refresh. Then, by the time the primary shard executes its first subpipeline, it already has the relevant information about the collection and doesn't need to target shards.

We should change the test to allow for both cases and audit for other related issues in the same file.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 04/Oct/21 ]

Author:

{'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}

Message: SERVER-60384: Fix race in lookup/graphLookup execution test
Branch: master
https://github.com/mongodb/mongo/commit/ee1b091cf1b3ad4c07903c5f8cfe4cdabfebdd8f

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