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

Drop pending reaper must not delete the _dropPendingNamespaces entry until after the drop occurs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.6, 4.0.0-rc0
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Storage NYC 2018-05-07

      Description

      Otherwise waiters on the drop will proceed before the drop finishes. Waiters call getEarliestDropOpTime() to determine until what optime they should wait, and getEarliestDropOpTime() looks at _dropPendingNamespaces to determine that.

      getEarliestDropOpTime() can currently see that _dropPendingNamespaces is empty, when there are still pending-drops to be completed, and return boost::none – or some misinformed answer --, which tells the caller that there's nothing for which to wait.

      Discovered while testing SERVER-33244's patch on no_implicit_collection_creation_in_txn.js

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: