[SERVER-75146] Investigate failures and re-enable allow_partial_results_with_maxTimeMS.js Created: 22/Mar/23  Updated: 04/Sep/23

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Peter Volk
Resolution: Unresolved Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-75145 Temporarily disable allow_partial_res... Closed
Related
Assigned Teams:
Query Optimization
Participants:
Linked BF Score: 160

 Description   

This test was temporarily disabled in SERVER-75145, to give us some breathing room.

This ticket tracks the work to get to the bottom of what happened so that we can fix the test or server and turn the test back on.



 Comments   
Comment by Steve Tarzia [ 31/Mar/23 ]

On second thought, my last comment may be incomplete because the BFG list also shows failures on macos-arm64 variants with an optimized build.

Comment by Steve Tarzia [ 31/Mar/23 ]

I did some testing on my virtual workstation and found that the test passes consistently on an optimized build but fails consistently on a debug build. The partial results functionality is very sensitive to timing. We had to tune the time allocated to shard execution vs router aggregation (currently 75%/25%). It will be difficult to tune this split to work well on both optimized and debug builds.

Can we just exclude this test from debug variants?

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