[SERVER-36848] Bumping txnNumber on Session must always abort running transaction with lower txnNumber Created: 24/Aug/18  Updated: 29/Oct/23  Resolved: 08/Oct/18

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.1.4

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: disabled-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-36799 Move transaction related functionalit... Closed
Related
related to SERVER-36847 Procedure to abort in-progress transa... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-10-08, Sharding 2018-10-22
Participants:
Linked BF Score: 21

 Description   

If a transaction with a higher txnNumber is started, but it fails validation and uasserts in TransactionParticipant::beginOrContinue() prior to aborting the previous transaction, then the txnNumber on the Session will be the new value, but there will still be an in-progress transaction in TransactionParticipant. The in-progress transaction is no longer accessible, since the txnNumber on Session has been bumped, so a client cannot abort it. We should never bump the txnNumber on Session without aborting the previous transaction.



 Comments   
Comment by Githook User [ 08/Oct/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: Revert "SERVER-36848 Temporarily blacklist snapshot_read_kill_op_only.js."

This reverts commit ebb653a9bdcb6ba1f1d4cc8113d32cdb86e6d2bb.
Branch: master
https://github.com/mongodb/mongo/commit/82a07e2f04f47de1602885ba00ecbca0ee72fc3f

Comment by Githook User [ 29/Aug/18 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-36848 Temporarily blacklist snapshot_read_kill_op_only.js.
Branch: master
https://github.com/mongodb/mongo/commit/ebb653a9bdcb6ba1f1d4cc8113d32cdb86e6d2bb

Comment by Tess Avitabile (Inactive) [ 24/Aug/18 ]

Assigning to the Sharding team, since this is a result of the Session refactor.

Generated at Thu Feb 08 04:44:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.