killSessions should kill transactions prior to killing cursors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0-rc0
    • Affects Version/s: 3.7.9
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-05-07, Repl 2018-05-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This will help prevent killSessions from blocking on locks held by a transaction it plans to kill.

      A suggested ordering for session kill is:

      1. Kill transactions
      2. Kill operations
      3. Kill cursors

            Assignee:
            Tess Avitabile (Inactive)
            Reporter:
            James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: