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

yieldLocksForPreparedTransactions while calling killSessionsAction should set the kill reason as ErrorCodes::InterruptedDueToStepDown if it is called during step down.

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.13
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Repl 2019-04-22, Repl 2019-06-03

      Currently yieldLocksForPreparedTransactions while calling killSessionsAction, it doesn't pass the reason for killing the operation. As a result, if we call yieldLocksForPreparedTransactions during step down, the operation (that checked out the session) will be mark killed with default reason "ErrorCodes::Interrupted".

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: