[SERVER-51140] Investigate how importCollection interacts with movePrimary Created: 24/Sep/20  Updated: 29/Oct/23  Resolved: 15/Oct/20

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

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

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-10-19
Participants:

 Description   

In createCollection, we have a check for movePrimary. This is a ticket to figure out whether we will need to do the same for importCollection.



 Comments   
Comment by Githook User [ 15/Oct/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-51140: Ban importCollection on sharded clusters
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/bf8a58490f0c8e166e398f7291b47b44f11743e9

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