Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Catalog, Sharding
Labels:
- sharding-common-backlog

Assigned Teams:

Sharding EMEA
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

in ~~SERVER-33272~~ we made empty databases proactively vanish as soon as they become empty, but this only was noticeable on non-sharded replica sets.
This ticket is to extend that behavior to sharding, so that when a config server knows that all collections in a database have been dropped, it can automatically drop such a database.

depends on

SERVER-33272 The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.

Closed

is related to

SERVER-33272 The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.

Closed

SERVER-77281 Investigate removing use of the DatabaseHolder and/or dropDatabase oplog entry in the storage execution layer

Closed

Assignee:: [DO NOT USE] Backlog - Sharding EMEA
Reporter:: Eric Milkie
Participants:: [DO NOT USE] Backlog - Sharding EMEA, Eric Milkie
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 02 2019 06:43:50 PM UTC
Updated:: May 25 2023 08:24:31 AM UTC
Resolved:: May 25 2023 08:24:31 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates