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

Profiling in transactions should only be interrupted due to lock acquisition failure

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • v4.0

    Description

      SERVER-34726 removes the UninterruptibleLockGuard protecting lock acquisitions for profiling of transaction operations. This is done to allow lock acquisitions for profiling of transaction operations to have a maxTransactionLockRequestTimeoutMillis timeout. However, the UninterruptibleLockGuard also prevented checking whether the operation was interrupted or timed out, which is desirable behavior. We would like profiling for transaction operations to succeed if the operation was interrupted or timed out, while preserving the maxTransactionLockRequestTimeoutMillis lock acquisition timeout.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: