[SERVER-45482] AutoGetCollectionForReadGlobalLockDeadline test can fail to obtain global lock within timeout of 0ms Created: 10/Jan/20  Updated: 27/Mar/20  Resolved: 26/Mar/20

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

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-46034 flake: deadline of `now` fails interm... Closed
Operating System: ALL
Sprint: Execution Team 2020-03-23, Execution Team 2020-04-06
Participants:

 Description   

The AutoGetCollectionForReadGlobalLockDeadline test attempts to acquire an exclusive global lock with a deadline of Date_t::now(). If any background operations which take locks are occurring at the time of the acquisition, the test will fail.

It should be safe to set the deadline to Date_t::max() to remove the timing dependency of the global lock acquisition, since the timing dependent part of the test happens after said acquisition.



 Comments   
Comment by Maria van Keulen [ 26/Mar/20 ]

The issue has already been addressed in SERVER-46034.

Generated at Thu Feb 08 05:08:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.