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

Add readConcern and readTimestamp to transaction sub-document of currentOp

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2018-06-18, Repl 2018-07-02, Repl 2018-07-16, Repl 2018-07-30

      Description

      We want the currentOp entry for both active and inactive transactions to contain an entry with a transaction.parameters sub document that contains the readConcern and the readTimestamp of the transaction. The readConcern we output here should be the readConcern after any potential upconvert, which should be stored in ReadConcernArgs::_level. The read timestamp should be stored on the session.

      For active transactions, the CurOp::reportCurrentOpForClient method should attach this information to the appropriate sub-document, and for inactive transactions, the Session::reportStashedState method should attach it.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jinny.byun Jinny Byun
              Reporter:
              william.schultz William Schultz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: