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

dropDatabase after step down can cause fassert

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.3, 3.7.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2018-01-01, Repl 2018-01-15
    • Linked BF Score:
      0

      Description

      If there is a step down, we return early and fail, but we never take the database out of the "drop pending" state. Thus if a new dropDatabase oplog entry comes in after the step down, it can cause an error in oplog application and a crash.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31436 dropDatabase must check `ReplicationCoordinator::canAcceptWritesFor` after reacquiring global lock

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: