[SERVER-71452] allow_partial_results_with_maxTimeMS.js assumes find is sorted by _id, and timeout is too short Created: 17/Nov/22  Updated: 29/Oct/23  Resolved: 18/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc2, 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:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.2
Sprint: QE 2022-11-28
Participants:
Linked BF Score: 46

 Description   

The FindWhereSleepController in allow_partial_results_with_maxTimeMS.js assumes that find will return documents in _id order, and that tends to happen when testing locally, but that's not guaranteed by WiredTiger. We should add a .hint({_id: 1}).

Also, ampleTimeMS was recently changed from a minimum of 2 seconds to just 100ms. This appears to be too short, and the change corresponds to the appearance of BF-26974. This timeout change should be reverted.



 Comments   
Comment by Githook User [ 18/Nov/22 ]

Author:

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

Message: SERVER-71452 hint _id index and lengthen timeout in allow_partial_results_with_maxTimeMS.js
Branch: v6.2
https://github.com/mongodb/mongo/commit/39881664f2a9478b2ed2aeb860448fb3c6291ab0

Comment by Githook User [ 18/Nov/22 ]

Author:

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

Message: SERVER-71452 hint _id index and lengthen timeout in allow_partial_results_with_maxTimeMS.js
Branch: master
https://github.com/mongodb/mongo/commit/dbc301d34503f263c5774e07b621684e39f1163e

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