[SERVER-33681] Test and document behavior of running abortTransaction and commitTransaction against snapshot reads Created: 05/Mar/18 Updated: 06/Dec/22 Resolved: 27/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
Running abortTransaction or commitTransaction with a txnNumber of a snapshot read (non-multi-statement transaction) should do something reasonable and have tests and documentation. It would be reasonable to either abort the transaction (following the same abort path we would take by bumping the txnNumber) or return an error that the txnNumber does not correspond to a multi-statement transaction. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 09/Mar/18 ] |
|
Sending to the repl team for at least initial suggestions on design since actually doing this will block on addition of commitTransaction and abortTransaction (which is on the repl team at the moment.) |