Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Blocker - P1 Blocker - P1
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.2, 1.7.0
    • Component/s: None
    • Labels:
      None
    • Backport:
      No
    • Operating System:
      ALL
    • # Replies:
      1
    • Last comment by Customer:
      false

      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.

        Activity

        • Comments
        Hide
        Eliot Horowitz
        added a comment -

        commit e070747d94e0dccfcab5ba2e385eb699c6993796

        Show
        Eliot Horowitz
        added a comment - commit e070747d94e0dccfcab5ba2e385eb699c6993796

          People

          • Assignee:
            Eliot Horowitz
            Reporter:
            Eliot Horowitz
            Participants:
            Last commenter:
            Ian Whalen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since reply:
              3 years, 34 weeks, 1 day ago