[SERVER-30499] Only update sessions with a transaction number Created: 03/Aug/17  Updated: 30/Oct/23  Resolved: 03/Aug/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.12

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-08-21
Participants:

 Description   

There are a few places in op_observer_impl.cpp and oplog.cpp that call

{set,get}

LastWriteOptimeTs or saveTxnProgress if a session exists on the operation context, but they should instead check the operation context has a transaction number, because the session's state isn't loaded without one.

SERVER-30281 adds invariants that _txnRecord has been set when some of these methods are called, so they will start to fail in the fuzzer.



 Comments   
Comment by Githook User [ 10/Aug/17 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-30499 Only update sessions with a transaction number
Branch: master
https://github.com/mongodb/mongo/commit/f5d9a6cbf83d18efa11150a24e1140ec2bb96d30

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