Don't kill already completed op in SessionWorkflow

XMLWordPrintableJSON

    • Service Arch
    • Fully Compatible
    • Service Arch 2023-10-30, Service Arch 2023-11-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This code currently calls killAndDelistOperation() for an operation that has already completed. Instead it should just delist the operation. Killing the op is currently more expensive than it should be due to baton inefficiency (I'll file a linked ticket for that soon SERVER-81793), but even once that is fixed, it will still be cheaper not to kill the op.

      This was measured to be the cause of a few percent of the findOne request latency.

            Assignee:
            Erin McNulty
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: