Remove assertNoMovePrimaryInProgress from MigrationChunkClonerSourceOpObserver

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Declined
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2025-10-13
    • 0
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      In the observer (after the successful write) there is no sense to assert if we have a movePrimary in progress as the modification already happened successfully.

            Assignee:
            Wolfee Farkas
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: