[SERVER-33213] Track find commands with txn machinery Created: 08/Feb/18 Updated: 06/Dec/22 Resolved: 20/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Even though reads don't need to worry about retryability in the same way writes do, they still consume a stmtId, so they still need to be tracked by the txn machinery so we can guarantee that we don't re-use a stmtId. |
| Comments |
| Comment by Ratika Gandhi [ 20/Sep/19 ] |
|
Will be picked up if the design of the epic recommends it. |
| Comment by Spencer Brody (Inactive) [ 06/Apr/18 ] |
|
This ticket should result in no user or driver-visible behavior changes. This is just about internal plumbing to track the stmtId associated with find commands in our in-memory transaction state. This plumbing will enable future validation that retried operations within a transaction don't re-use a stmtId incorrectly. |