Log all failed transaction statements

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • None
    • Repl 2019-04-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Tess Avitabile (Inactive)
            Reporter:
            Bruce Lucas (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: