Update the oldest_id before the drop table active transaction check

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: Transactions
    • None
    • Storage Engines, Storage Engines - Transactions
    • SE Transactions - 2025-05-09
    • 3

      WT-10576 has introduced the active transaction check as part of the drop command before proceeding with the drop operation. The active transaction check was to verify whether the last modified transaction on the table is globally visible or not.

      The⁣ {oldest_id}} that is used for the transaction global visibility is calculated or updated regularly in different code paths of the WT. In some scenarios, if this oldest_id is not updated, the drop command can fail with an EBUSY error even if there are no other older transactions present in the system.

      To fix this problem, update the oldest_id before performing the active transaction check during the drop operation.

            Assignee:
            Haribabu Kommi
            Reporter:
            Haribabu Kommi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: