-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
In 3.6, the behavior of the dropDatabase command changed a bit. What we now do is:
- Take the global exclusive lock
- Mark the database as drop-pending, which will prevent new collections from being created on the database
- Drop every collection in the database
- Release the global exclusive lock
- Wait for the collection drops to replicate to a majority
- Re-take the global exclusive lock
- Drop the database catalog entry
- Release locks and return
- [optionally wait for user-provided write concern to replicate the write that dropped the database catalog entry]
- is related to
-
DOCS-10541 Docs for SERVER-29277: Two Phase Drops: implement dropDatabase changes to support 2-phase drops
- Closed