[SERVER-42053] proactively drop newly empty databases (sharding) Created: 02/Jul/19  Updated: 25/May/23  Resolved: 25/May/23

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

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Fix Votes: 0
Labels: sharding-common-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-33272 The DatabaseHolder::close() function ... Closed
Related
is related to SERVER-77281 Investigate removing use of the Datab... Backlog
is related to SERVER-33272 The DatabaseHolder::close() function ... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

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.



 Comments   
Comment by Eric Milkie [ 02/Jul/19 ]

This work depends on the ability of the config server to know about all collections, including unsharded ones, so this ticket depends on that project's completion.

Generated at Thu Feb 08 04:59:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.