Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-40306

Lock acquisition in dropDatabase cmd can throw and leave the database with drop-pending set to true

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.10
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2019-04-08
    • 9

    Description

      The dropDatabase cmd is getting stalled on lock acquisition here after waiting for replication of the dropCollection ops, before executing the dropDb logic that can proceed once the collections are gone. We have several Guards in the dropDatabase logic to unset the drop-pending flag if there are any errors, but that lock acquisition is not guarded, the previous guard being released here and a new guard not set until afterwards here, creating a window of opportunity. Lock acquisition can throw now.

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: