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

Make CleanUpForMigrateIn deterministic

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.10
    • Affects Version/s: 4.4.9
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
    • 58

      The unit test CleanUpForMigrateIn checks theĀ number of ranges to clean after waiting for the future returned by beginReceive to finish. However, the range is only removed after an asynchronous callback is completed. This creates a race condition in this test between the assertion that there are no ranges to clean and the deletion of the range deletion task from the list.

      The test is not actually using the assertions causing the problem, so the solution is simply to remove them.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: