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

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.6
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Repl 2018-04-23
    • 13

      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.

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

              Created:
              Updated:
              Resolved: