[SERVER-36484] Set multi-document transaction timeout to infinite for prepared transactions Created: 07/Aug/18 Updated: 27/Oct/23 Resolved: 14/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | prepare_errors | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Sprint: | Repl 2018-08-27 |
| Participants: |
| Comments |
| Comment by Kaloian Manassiev [ 14/Dec/18 ] |
|
The expired() check on the transaction participant already checks whether the transaction is prepared, so it will not be attempted to be aborted. |
| Comment by Judah Schvimer [ 23/Aug/18 ] |
|
It's not necessary to set the timeout to infinite if there is another mechanism for making sure that prepared transactions are not aborted. The only reason to change the timeout explicitly would be for diagnostics. |