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

Include the connection ID in the abortExpiredTransactions log entry

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Backlog
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Logging
    • Labels:
      None

      Description

      When the abortExpiredTransactions operation is logged, it contains the following information:

      2020-08-03T09:45:57.170+0000 I  TXN      [abortExpiredTransactions] transaction parameters:{ lsid: { id: UUID("aaaa"), uid: BinData(0, bbbb) }, txnNumber: 1, autocommit: false, readConcern: { level: "snapshot" } }, readTimestamp:Timestamp(0, 0), ninserted:1 keysInserted:1 terminationCause:aborted timeActiveMicros:49 timeInactiveMicros:79530719 numYields:0 locks:{ ReplicationStateTransition: { acquireCount: { w: 3 } }, Global: { acquireCount: { w: 2 } }, Database: { acquireCount: { w: 2 } }, Collection: { acquireCount: { w: 2 } }, Mutex: { acquireCount: { r: 2 } } } storage:{} wasPrepared:0, 79530ms
      

      It'd be helpful to add the connId as a transaction parameter so that we can correlate to a certain connection and get a better sense of which application was associated with this event.

        Attachments

          Activity

            People

            Assignee:
            gaurav.gk Gaurav Kumar
            Reporter:
            tomer.yakir Tomer Yakir
            Participants:
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Dates

              Created:
              Updated: