[SERVER-68806] Always put the readTimestamp on currentOp when we have one Created: 12/Aug/22 Updated: 06/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng, storex-ranked | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Participants: |
| Description |
|
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. |
| Comments |
| Comment by Connie Chen [ 16/Aug/22 ] |
|
we may want to add readConcern and whether the user specified it. |