Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11488

Document that dropDatabase in 3.6 now waits for replication internally

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • None
    • manual
    • None

    Description

      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]

      Attachments

        Activity

          People

            Unassigned Unassigned
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              5 years, 46 weeks, 2 days ago