ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1025
    • Affects Version/s: 9.1.0-rc0, 9.1.0-rc1025
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-11-09
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In chunk_migration_range_deletion_deprioritization.js, we currently wait for config.rangeDeletions to become empty, then immediately check that totalDeprioritizations increased.
      However, SERVER-137376 changed the underlying test assumption that once the task document disappears, the counter has already increased. After SERVER-137376, this ordering is no longer guaranteed and the persistent task document can be removed before the worker’s operation context is destroyed and its statistics are finalized.

      Therefore, as part of this ticket, we must assert.soon to wait until getTotalDeprioritizationCount(donorPrimary) is greater than donorCountDeprioritizableBeforeRangeDeletion.

            Assignee:
            Anna Maria Nestorov
            Reporter:
            Anna Maria Nestorov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: