[SERVER-14678] Cleanup leftover collection metadata after drop Created: 25/Jul/14  Updated: 06/Dec/22  Resolved: 03/Dec/21

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

Type: Improvement Priority: Major - P3
Reporter: David Hows Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-17397 Dropping a Database or Collection in ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Currently we do very limited cleanup of the config metadata following the drop of a database.

We should add processes to cleanup old config entries, specifically:

  1. config.collections
  2. config.locks

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