[SERVER-43180] removeShard command run with forceRemoveByAbandoningData should move the db primary for any dbs whose primary is the shard to be removed Created: 05/Sep/19  Updated: 06/Dec/22  Resolved: 03/Jan/20

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

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

The removeShard does not run movePrimary for any databases whose primary is the shard being removed currently. When run with the new option "forceRemoveByAbandoningData", the command should run movePrimary for the dbs and avoid the need for any user manual intervention.



 Comments   
Comment by Sheeri Cabral (Inactive) [ 03/Jan/20 ]

We have abandoned the project associated with this work - PM-1477.

Generated at Thu Feb 08 05:02:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.