[SERVER-42404] Merge beginOrContinue() and unstashTransactionResources() in TransactionParticipant Created: 24/Jul/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
Start and unstash should conceptually happen at the same time. Merging them together could make transaction state manipulation easier to avoid the complexity as we have seen inĀ |
| Comments |
| Comment by Siyuan Zhou [ 25/Jul/19 ] |
|
suganthi.mani, the merged function should guarantee it aborts unprepared transactions on throwing exceptions by itself. |
| Comment by Suganthi Mani [ 24/Jul/19 ] |
|
FYI, due to this reason, we are not wrapping an error guard for beginOrContinue. So, I am not sure whether merging can take place. |