[SERVER-72007] allow_partial_results_with_maxTimeMS_failpoints.js can timeout before getMore Created: 09/Dec/22  Updated: 29/Oct/23  Resolved: 15/Dec/22

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

Type: Bug Priority: Major - P3
Reporter: Steve Tarzia Assignee: Steve Tarzia
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
Steps To Reproduce:

I have not reproduced this locally, because it seems to require competing tasks to consume resources in the background, but we have a cold BF that suggests this is happening: BF-26792.

Sprint: QE 2022-12-12, QE 2022-12-26
Participants:
Linked BF Score: 16

 Description   

As seen in BF-26792, it's possible for allow_partial_results_with_maxTimeMS_failpoints.js to unexpectedly return a MaxTimeMSExpired error on the initial find (line 289) of the test that looks for timeouts in a getMore.  This happens in roughly 5% of evergreen runs, probably when resources are limited after the ampleTimeMS is calculated.

To avoid this unexpected timeout, we can set the "maxTimeNeverTimeOut" failpoint.



 Comments   
Comment by Githook User [ 15/Dec/22 ]

Author:

{'name': 'Steve Tarzia', 'email': 'steve.tarzia@mongodb.com', 'username': 'starzia'}

Message: SERVER-72007 Never timeout in initial find before getmore in allow_partial_results_with_maxTimeMS_failpoints.js
Branch: master
https://github.com/mongodb/mongo/commit/7c6b37be1db235709693ce14d655ba4244c4bcc0

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