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

Implement movePrimary on the shards

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.7.1
    • Component/s: Sharding
    • Labels:
      None
    • Sharding

      1. Call the ‘clone’ command on the new primary
        1. sync collection options (ttl expiration requires special handling)
        2. sync indexes
        3. copy db.system.views
      2. Write the minOpTimeRecovery document and enter a critical section
      3. Send a (new) ‘commitMovePrimary’ command to the config server
      4. Invalidate cached database entry
        1. Involves infrastructural changes to add a “DatabaseMetadata” (equivalent to CollectionMetadata) on shards

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: