[DOCS-16264] [Server] Investigate changes in SERVER-78855: Use snapshot isolation for Queryable Encryption transactions Created: 14/Jul/23  Updated: 13/Nov/23  Resolved: 20/Jul/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc8, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Sarah Simpers
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-16265 [BACKPORT] [v7.0] Use snapshot isolat... Closed
Documented
documents SERVER-78855 Use snapshot isolation for Queryable ... Closed
Duplicate
is duplicated by DOCS-16265 [BACKPORT] [v7.0] Use snapshot isolat... Closed
Participants:
Days since reply: 29 weeks, 5 days ago
Story Points: 2

 Description   
Original Downstream Change Summary

Sharded transactions that use Query Encryption must set readConcern: snapshot. Other readConcern levels (local, majority) are disallowed. QE uses readConcern for internal transactions implicitly.

Replica Set transactions have no limitations.

Description of Linked Ticket

Use of distributed transactions involving multiple collections makes it more likely that users of QE will hit SERVER-77506. Until it's resolved we should upgrade transactions used as part of QE to use snapshot read concern.


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