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

Add RecoveryUnit debug logs to WT::begin_transaction() calls

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution
    • 0

    Description

      We have a test failure wherein an error occurs to the effect that a WT transaction is already open when the MDB layer calls WT::begin_transaction – it has already been called once and calling it again is not supported.

      It isn't obvious where the issue is, that the MDB layer is double calling or not. The RecoveryUnit is supposed to track state for storage engine access – active, inactive, WUOW, etc. --, so it might be helpful to log some of that information before proceeding to call invariantWTOK on the WT::begin_transaction() calls. Assuming the RecoveryUnit doesn't have a bug, that is. Hopefully RU state will be enlightening regardless.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: