Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:
None

Assigned Teams:

Sharding
Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Sharding admin operations were designed with a small number of cluster admin users in mind, but are increasingly being used directly. Better synchronize all these operations.

is depended on by

SERVER-4724 removeShard needs to take into account asynchronous document deletion after migrate

Closed

is duplicated by

SERVER-6105 Dropping sharded collection and recreating it confuses mongos

Closed

SERVER-8959 Better story for mongos refresh when another mongos dropped a database

Closed

SERVER-9496 Drop sharded collection the drop of sharded db leaves data on non-primary shards

Closed

is related to

SERVER-4355 Support multiple parallel chunk migrations for the same collection

Closed

Assignee:: [DO NOT USE] Backlog - Sharding Team
Reporter:: Greg Studer (Inactive)
Participants:: [DO NOT USE] Backlog - Sharding Team, Gregory McKeon, Greg Studer
Votes:: 3 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Dec 21 2011 04:45:59 PM UTC
Updated:: Dec 06 2022 05:38:14 AM UTC
Resolved:: Mar 21 2018 07:29:42 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates