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

cursor tracking is not database aware

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.2, 1.7.0
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL

      Description

      We track cursors by object location so if an object is deleted we can advance.
      We weren't keep these isolated by db, so if a cursor is open at position X on db A, and a delete on db B removes an object at position X, a segfault can happen because a cursor will be advanced to an illegal position.

      This is exacerbated by replication because once an oplog rolls over, every time we add an op, we delete one, so it makes the odds of this higher.

        Attachments

          Activity

            People

            • Assignee:
              eliot Eliot Horowitz
              Reporter:
              eliot Eliot Horowitz
              Participants:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: