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

Improve transaction lock failure error message

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Diagnostics
    • Labels:
      None
    • Fully Compatible
    • Execution Team 2019-07-01

      The error message when a transaction statement is unable to acquire a lock within the timeout is cryptic, making it difficult to identify the conflicting operation:

      Unable to acquire lock '{7817449386782089629: Database, 899920359141007773}'

      Would it be possible to include more information that could help pinpoint the cause of the conflict, for example

      • conflicting database or collection name
      • connection number of client holding the lock
      • operation id holding the lock
      • name of operation holding the lock

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: