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

Investigate killop in ClientCursor::aboutToDelete()

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Concurrency
    • Labels:

      I think there may be a case similar to SERVER-5999 where a kill op request to a remove operation that has not yet performed a write can trigger an interrupt exception inside a cursor advance() in ClientCursor::aboutToDelete(). This could leave a MultiCursor in an inconsistent state, as in SERVER-5999. Worth investigating and fixing if necessary.

            Assignee:
            Unassigned Unassigned
            Reporter:
            aaron Aaron Staple
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: