[SERVER-38733] Change majority read concern transaction passthroughs to use local read concern Created: 20/Dec/18  Updated: 29/Oct/23  Resolved: 03/Jan/19

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

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

Issue Links:
Related
related to SERVER-33983 Add support for transactions in readC... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-12-31, Sharding 2019-01-14
Participants:

 Description   

To get coverage of read your own writes behavior for local operations on a single node without causal consistency without failovers, there should be transaction passthrough suites that use transactions with "local" read concern and commit with w:1 write concern in non-causally consistent sessions. Non transaction operations should also use these read and write concerns.

This can be done by changing the existing concurrency_sharded_replication_majority_multi_stmt_txn(_with_balancer) suites to use "local" read concern instead of "majority." These suites already commit with w:1 write concern.

The existing multi_shard_majority_multi_stmt_txn suite should also be changed to use "local" read concern and its commit write concern should be changed from w:majority to w:1.



 Comments   
Comment by Githook User [ 03/Jan/19 ]

Author:

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

Message: SERVER-38733 Change majority read concern transaction passthroughs to use local read concern
Branch: master
https://github.com/mongodb/mongo/commit/4be5caeab1810c7c58f205f5eaf66cf97fb07b9e

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