[SERVER-79401] Investigate interactions between multi-document transactions and assertReadConcernSupported Created: 27/Jul/23  Updated: 03/Nov/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: car-qw, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Sprint: Execution EMEA Team 2023-10-16
Participants:
Story Points: 3

 Description   

The assertReadConcernSupported method is only used by the AutoGetCollectionForRead* family of AutoGetters. As a result, normal AutoGetCollection calls are exempted from that check.

For SERVER-77507 we integrated the assertion check into collection acquisitions and had to exempt writes from performing that check. Ideally, we would want to expand that assertion to everyone but doing so leads to this code causing issues. The transaction is writing to the config.transactions collection with the original read concern settings, leading to this assertion being hit.


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