Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-86147

Handle cluster to cluster migrations (such as tenant migrations / shard merge / split etc.) when recordIdsReplicated:true

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      Tenant migrations and the other migrations listed above happen via the recipient primary, which means that as the data is copied over the recipient primary inserts it. As long as the recipient primary knows that the collection being copied has recordIdsReplicated:true (which may be something we need to implement - the primary probably won't know this), then from that point onward replication will ensure that the recordIds are the same (thanks to SERVER-78348 / SERVER-86046).

      However, the recordIds will NOT be the same as the recordIds on the source cluster, which should be OK.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: