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

Always put the readTimestamp on currentOp when we have one

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

      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:
            backlog-query-integration [DO NOT USE] Backlog - Query Integration
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: