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

Deadlock exceptions thrown during delete unsafe and skip documents

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Concurrency, Querying
    • Labels:
      None
    • Operating System:
      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

          Issue Links

            Activity

              People

              Assignee:
              greg_10gen Greg Studer
              Reporter:
              greg_10gen Greg Studer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: