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

Race in WaitWithOpTimeEarlierThanLowestQueued causes it to fail

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Sharding 2019-08-12
    • 43

      Most of the time, when the 2nd wait is queued, the background thread has not picked up the first wait yet, so it just cut in the line as expected. However, if the 2nd request is called and the background thread is already in the middle of waiting, it will get signalled instead. Before SERVER-42335, it will cause the future to become ready since it was not propagating the signal properly. After SERVER-42335, it will cause the test to hang because it is waiting for the future of the 2nd wait and was not expecting the 1st wait to "consume" the wait.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: