[SERVER-29852] Store logical session id and transaction number on the OperationContext Created: 26/Jun/17  Updated: 30/Oct/23  Resolved: 27/Jun/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.9
Fix Version/s: 3.5.10

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-10444 Docs for SERVER-29852: Store logical ... Closed
Related
related to SERVER-30936 Attempting to create an existing shar... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-07-10
Participants:

 Description   

The lsid and txnNumber fields will become legitimate top-level values for all commands. As such, there should be code just after command parsing, but before authentication (so the sessionId is available to the auth system), which extracts these fields and sets them on the OperationContext.



 Comments   
Comment by Githook User [ 27/Jun/17 ]

Author:

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

Message: SERVER-29852 Store session id and transaction number on all commands' OperationContext
Branch: master
https://github.com/mongodb/mongo/commit/8fe4426fa36587ca40a0b6c8f1c84fd9aa61e5cf

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