[SERVER-53061] Empty database directory will not be removed if collection ident is not dropped before all index idents Created: 24/Nov/20  Updated: 29/Oct/23  Resolved: 08/Jan/21

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

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-51717 Empty database directory will not be ... Closed
related to SERVER-48882 If directoryperdb is active, remove e... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-12-28, Execution Team 2021-01-11
Participants:
Linked BF Score: 13

 Description   

When removing an empty database directory using directoryperdb, the collection ident drop is what runs the callback to remove the directory. This is based on the fact that we drop the collection ident after the index idents. However, since the WT ident drops can be queued and may not actually be dropped in the same order, we cannot rely on this assumption. We should make sure that the callback runs on the final ident drop, regardless of whether it's a collection or an index ident.



 Comments   
Comment by Ian Whalen (Inactive) [ 09/Jan/21 ]

Author:

{'username': u'evrg-bot-webhook', 'name': u'Gregory Noma', 'email': u'gregory.noma@gmail.com'}

Message:SERVER-53061 Attempt to remove empty database directory on both collection and index ident drop
Branch:master
https://github.com/mongodb/mongo/commit/a2bd60fb04358ce7250c87477365a26b660b907a

Generated at Thu Feb 08 05:29:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.