Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45482

AutoGetCollectionForReadGlobalLockDeadline test can fail to obtain global lock within timeout of 0ms

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Concurrency
    • None
    • ALL
    • Execution Team 2020-03-23, Execution Team 2020-04-06

      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.

            Assignee:
            maria.vankeulen@mongodb.com Maria van Keulen
            Reporter:
            maria.vankeulen@mongodb.com Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: