[SERVER-80254] Refactor lookup_unionWith_subpipeline_local_read.js to avoid asserting on exact number of local/remote reads Created: 18/Aug/23  Updated: 24/Aug/23  Resolved: 24/Aug/23

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

Type: Improvement Priority: Major - P3
Reporter: Ben Shteinfeld Assignee: Ben Shteinfeld
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-80255 Refactor lookup_unionWith_subpipeline... Closed
Participants:

 Description   

lookup_unionWith_subpipeline_local_read.js is structured to execute pipelines with subpipelines in various topologies and inspect profiler entries to assert that a certain number of the subpipeline invocations where performed as remote vs local reads. However there are an increasing number of complex race conditions which affect the exact number of local vs remote reads that are done, becoming a cause of non-trivial BFs. But in the majority of cases, we really only care whether local reads were performed or not, we don't care exactly how many there were.

The task of this ticket is to refactor the test to avoid asserting on an exact number of local/remote reads, making it more robust.



 Comments   
Comment by Ben Shteinfeld [ 22/Aug/23 ]

https://github.com/10gen/mongo/pull/15013

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