[SERVER-4856] movePrimary should fail if any sharded and undrained collections exists in db Created: 02/Feb/12  Updated: 19/Apr/12  Resolved: 03/Feb/12

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

Type: Bug Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Duplicate Votes: 0
Labels: movePrimary, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-3562 moveprimary moves all databases, incl... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

For now (temporarily) fail if there are any sharded collections (un-drained) in the database you are moving to a new shard.

In the future we should fix this in a better way, to not just fail fast.


Generated at Thu Feb 08 03:07:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.