movePrimary should set dbversion on recipient shard

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, the movePrimary coordinator leaves the database version both on the donor and destination shard as UNKNOWN. Instead, we should make it so that before living the critical section, both donor and recipient have the correct db version installed in DSS.

            Assignee:
            Unassigned
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: