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

Log all failed transaction statements

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Diagnostics
    • None
    • Repl 2019-04-08

    Description

      When diagnosing transaction failures due to issues such as write conflicts or inability to acquire a lock within the 5ms timeout it would be helpful if the failures were always logged even if they didn't exceed the slowms threshold.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-39955 Add support for a "comment" parameter to commit transaction

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-39985 Improve transaction lock failure error message

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-40329 Log all transactions at TXN verbosity levels >= 1

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              bruce.lucas@mongodb.com Bruce Lucas
              Votes:
              2 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: