Wait for range deletions to complete in migration_coordinator_failover_include.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability 19Jan-2Feb
    • 200
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-113354 introduced a change where we allow overlapping range deletion tasks to be registered and process them synchronously later. In migration_coordinator_failover_include.js we perform successive migrations without waiting for range deletions to complete that results in DuplicateKey error. The test should wait for range deletions before starting a new migration. Note that we do wait for documents to be deleted but it is not atomic with range deletion task document deletion.

            Assignee:
            Abdul Qadeer
            Reporter:
            Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: