[SERVER-37944] Update causally consistent txn passthroughs to send non-txn reads to secondaries Created: 06/Nov/18  Updated: 06/Dec/22  Resolved: 05/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: ShardedTxn:Testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37878 Run causally_consistent_jscore_txns_p... Closed
is related to SERVER-39139 Remove testing support for secondary ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

The existing causally consistent transaction passthroughs are mostly meant to ensure enabling causal consistency doesn't break the core transaction functionality, so they run against 1 node replica sets (e.g. sharded_causally_consistent_jscore_txns_passthrough). They also do so because currently transactions cannot read from secondaries. To better test causal consistency before transactions can run on secondaries, these suites could be updated to use multiple node replica sets and run all non-write commands that are not part of a transaction with secondary read preference and afterClusterTime read concern.


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