BugZero found this defect 60 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/20/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
In the read_pref_with_hedging_mode test, the first read that doesn't throw some error on the mongos is setting a maxTimeMS of 1000ms. Since this is the first read to this collection, the mongoS is having to perform a refresh to get the routing information. On slow machines, this refresh can sometimes take enough time that the operation hits the max time. We should either increase the maxTimeMS of this operation or perform a read at the beginning of the test to cause the refresh to happen earlier.