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

Drop collection command with majority write concern should wait until two-phase drop finishes

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.7.6
    • Replication
    • None
    • Fully Compatible
    • Repl 2018-04-23
    • 13

    Description

      Waiting for the drop command gets replicated to a majority doesn't guarantee the drop completes on the primary, so after the command returns, the drop-pending collection reaper will actually drop the collection, which takes the database lock in X mode. The asynchronous DB lock in X mode may be unexpected to users, especially transaction users, because it will block (or abort when SERVER-33244 is done) transactions waiting for the DB lock.

      Attachments

        Issue Links

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              siyuan.zhou@mongodb.com Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: