[SERVER-35709] mongos should remember readConcern setting for multi statement transaction Created: 20/Jun/18  Updated: 29/Oct/23  Resolved: 25/Jul/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.1.1
Fix Version/s: 4.1.2

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

Issue Links:
Related
related to SERVER-35825 mongos should allow readConcern for w... Closed
related to SERVER-36240 Make transactions on mongos use snaps... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-07-30
Participants:

 Description   

The readConcern setting is only sent on the first statement of the transaction. Mongos should remember to attach this setting when sending to shards it has not yet contacted on subsequent requests.



 Comments   
Comment by Githook User [ 25/Jul/18 ]

Author:

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

Message: SERVER-35709 Mongos should remember readConcern setting for multi statement transactions
Branch: master
https://github.com/mongodb/mongo/commit/46cdaa4d4c6f8c31e3635f67d4ab7b08692cd229

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