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

Race condition in shard_split_startup_recovery_aborted.js with abort timeout

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Server Serverless 2023-03-06, Server Serverless 2023-03-20, Server Serverless 2023-04-03, Server Serverless 2023-04-17
    • 5

      there is a race condition between setting up the timer and waiting for the failpoint. if the timer elapses before getting to the continuation where we wait for the failpoint, we'll just end up waiting forever.

      we could increase the timeout to make this less likely, but this will (a) slow down the test, and (b) not necessarily prevent this from happening in the future. perhaps an existing (or new) failpoint can be utilized, or some other means of testing the correct abort behavior without explicitly relying on a timeout.

            Assignee:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Reporter:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: