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

Deadlock exceptions thrown during delete unsafe and skip documents

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker - P1 Blocker - P1
    • None
    • None
    • Concurrency, Querying
    • None
    • ALL

    Description

      Also may occur during update - haven't dug in.

      When a deadlock exception is thrown in the DeleteStage, the stage is not restored before reusing via DeleteStage::restoreStage - this can allow a primary stepdown to go undetected or undetected cursor invalidation and is generally undefined behavior. Also, the DeleteStage does not store the working set member (WSM) when the problem occurs, so on resume the child stage will return the next member.

      Attachments

        Activity

          People

            greg_10gen Greg Studer
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: