Always put the readTimestamp on currentOp when we have one

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I noticed in the currentOp docs that we report readTimestamp for $currentOp.transaction.readTimestamp but I don't see why we shouldn't always report the read timestamp, when an operation has a read timestamp (be it externally or internally chosen). Hook into the recovery unit logic, maybe.

            Assignee:
            Unassigned
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: