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

Track transaction size on 4.0

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.9
    • Component/s: Diagnostics, Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2019-04-08

      Description

      Adding metrics around the size of transactions could help us determine what use cases to optimize for. Metrics for the last run transaction:

      1. Number of operations in the transaction
      2. Total size of transaction statements in oplog
      3. Write Concern

      There will be a new serverStatus section transactions.lastCommittedTransaction:

      {
      		 
          "operationCount" : NumberLong(1),
      		 
          "oplogOperationBytes" : NumberLong(151),
      		 
          "writeConcern": {
      		 
              "w" : 1,
      		 
              "wtimeout" : 0
      		 
          }
      		 
      }

        Attachments

          Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-13195 Investigate changes in SERVER-40372: Track transaction size on 4.2+

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

          Task - A task that needs to be done. SERVER-40372 Track transaction size on 4.2+

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

            Activity

              People

              Assignee:
              tess.avitabile Tess Avitabile
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: