New recipient primary can complete migration before donor renames collection in tenant_migration_resume_collection_cloner_after_rename.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.3, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • 17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After we step it up, the new recipient primary can complete the migration before we get a chance to rename the collection. We can prevent this by setting a failpoint to pause the migration on the new recipient and turning it off once we're done renaming the collection on the donor.

              Assignee:
              Vishnu Kaushik
              Reporter:
              Vishnu Kaushik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: