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

Increase AbortExpiredTransactionsSessionCheckoutTimeout in kill_op_on_txn_expiry.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Minor Change
    • ALL
    • Repl 2024-11-11
    • 0

      SERVER-77172  introduced a new code path that can terminate the session without logging this line.

      this situation can occur when the abortExpiredTransactions job takes longer than the gAbortExpiredTransactionsSessionCheckoutTimeout, which is set to 100 milliseconds, after the multi-statement transaction's OperationContext has been killed to check out its session.

      So for this test we need to set AbortExpiredTransactionsSessionCheckoutTimeout to a large value to not fail on slow machine.

            Assignee:
            m.maher@mongodb.com Moustafa Maher
            Reporter:
            m.maher@mongodb.com Moustafa Maher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: