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

Add abortCause to mongos transactions serverStatus output

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.0-rc3, 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • v4.2
    • Sharding 2019-06-17

      As per the scope document, track the number of each transaction abort cause on mongos and add them to the "transactions" field in its serverStatus output.

      This was spun off from SERVER-40984.

      Proposed Implementation

      • Add a string map of int64_t to RouterTransactionMetrics protected by a mutex
      • In each place about cause is saved per transaction, add the cause to the map as well
      • Output the map in the format from the scope by updating RouterTransactionMetrics::updateStats() and adding an "abortCause" document type to the RouterTransactionStats IDL type
      • Add unit / jstests
        • Update existing jstests/noPassthrough/router_transaction_metrics.js and/or add new cases to transaction_router_test.cpp

            Assignee:
            jamie.heppenstall@mongodb.com James Heppenstall (Inactive)
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: