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

OplogWriterImpl does not handle interruptions gracefully

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      It is technically possible for an overeager user to run killOp against user threads, which would result in opCtx's getting unexpectedly interrupted. In some cases (like against the OplogWriterImpl thread) this can lead to a server crash if it is not handled.

      This requires a user to have elevated privileges and kill an operation they have no reason to kill, but do we want to take action to prevent a server crash in instances like this?

            Assignee:
            Unassigned Unassigned
            Reporter:
            sean.zimmerman@mongodb.com Sean Zimmerman
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: