Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.2.1, 4.3.1
Affects Version/s: None
Component/s: Sharding
Labels:

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.2, v4.0, v3.6
Sprint:
Sharding 2019-05-06, Sharding 2019-06-17, Sharding 2019-07-15, Sharding 2019-07-29, Sharding 2019-08-12
Case:
Linked BF Score:
15

As described in ~~SERVER-17397~~, with the way sharded collection/database create and drop are implemented currently, it is possible that a failed create or drop operation might leave around partial information such as incomplete chunks or collection entries. This forces administrators to do manual cleanup and poses the risk of corrupting data due to human error.

We should implement `cleanupOrphanedCollection`/`cleanupOrphanedDatabase` commands, which perform this cleanup and do proper checking and synchronization.

The code for these manual commands will eventually become the basis for implementing consistent drops using a resumable task queue.

depends on

SERVER-41813 Allow ViewCatalog lookup without validating system views

Closed

is duplicated by

SERVER-17243 Dropped collection & database still has metadata

Closed

SERVER-21179 Clean-up orphan chunk entries left from a failed shardCollection with initial split

Closed

SERVER-6413 Validate shard tags and tag chunk regions when sharding collections

Closed

is related to

SERVER-17397 Dropping a Database or Collection in a Sharded Cluster may not fully succeed

Closed

Assignee:: Blake Oler

Reporter:: Kaloian Manassiev

Participants:: Blake Oler, Esha Maharishi, Githook User, Kaloian Manassiev

Votes:: 5 Vote for this issue

Watchers:: 19 Start watching this issue

Created:: Mar 19 2018 02:19:02 PM UTC

Updated:: Oct 29 2023 10:33:36 PM UTC

Resolved:: Aug 01 2019 06:08:57 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates