[SERVER-38133] When asked to continue a transaction whose txnNumber is too new, TransactionParticipant must abort that transaction Created: 14/Nov/18 Updated: 04/Jan/19 Resolved: 04/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | prepare_durability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Sprint: | Repl 2018-12-03, Repl 2018-12-17, Repl 2019-01-14 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
When TransactionParticipant::_continueMutliDocumentTransaction() is called with a txnNumber that is higher than _activeTxnNumber, it returns NoSuchTransation but does not update _activeTxnNumber or abort the transaction. It must set _activeTxnNumber to txnNumber and abort the transaction (with the new txnNumber). This ensures that no future command may start a transaction with this txnNumber, so the commit decision for this txnNumber cannot change. |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 04/Jan/19 ] |
|
Closing in favor of |