[SERVER-32611] Implement movePrimary on the shards Created: 09/Jan/18  Updated: 06/Dec/22  Resolved: 08/Feb/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.1
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   
  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


 Comments   
Comment by Esha Maharishi (Inactive) [ 08/Feb/18 ]

This was split into a few tickets in PM-1017, so closing as a dupe.

Generated at Thu Feb 08 04:30:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.