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

Make kill_cursors_in_transaction.js resilient to LockTimeout

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2023-12-11
    • 5

    Description

      Currently kill_cursors_in_transaction.js tries to test that killCursors does not block behind a pending MODE_X lock issued from a drop command. However, it is possible that ticket exhaustion may occur and that the killcursor command can fail with an "Unable to acquire ticket with mode '2' due to detected lock conflict", due to a detected deadlock. Since this is allowed behavior and killCursors is not considered to be blocked in this case, we should check if the error Msg is LockTimeout and rollback the transaction. This is done to address the issue in BF-30628.

      Attachments

        Activity

          People

            damian.wasilewicz@mongodb.com Damian Wasilewicz
            damian.wasilewicz@mongodb.com Damian Wasilewicz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: