Investigate if interrupting OperationContext can result in temproraily orphaned workerPool threads

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When killing the oplog application threads, it may be possible that the parent thread is killed before the threadPool tasks are killed.
      If this happens, then each OplogEntry in std::vector<OplogEntry> ops will be freed, and the child threads will have dangling pointers.

            Assignee:
            Unassigned
            Reporter:
            Joseph Obaraye
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: