[SERVER-36146] Refactor sharding movePrimary command to not use clone Created: 16/Jul/18  Updated: 29/Oct/23  Resolved: 24/Jul/18

Status: Closed
Project: Core Server
Component/s: Internal Code, Sharding
Affects Version/s: None
Fix Version/s: 4.1.2

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-36257 Remove copyDB and clone commands Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-07-30
Participants:

 Description   

The "clone" command will be removed as part of the Remove CopyDB project. The Sharding "movePrimary" command is internally implemented using the "clone" command, so it should be refactored to no longer rely on "clone".



 Comments   
Comment by Githook User [ 24/Jul/18 ]

Author:

{'username': 'mvankeulen94', 'name': 'Maria van Keulen', 'email': 'maria@mongodb.com'}

Message: SERVER-36146 Remove usage of clone command in _cloneCatalogData
Branch: master
https://github.com/mongodb/mongo/commit/7f729d704fbf683a8746c8a512a8fd694118e3e7

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