Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- sharding-nyc-subteam2

Assigned Teams:

Cluster Scalability
Operating System:
ALL
Story Points:
2
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The transaction router extracts the read concern settings here via beginOrContinue. However, in the command processing, we call beginOrContinue first, before applying the default settings to the operation context's read concern settings

is related to

SERVER-78949 Consider folding atClusterTime into readConcern object in TransactionRouter::SharedTransactionOptions

Backlog

related to

SERVER-79766 TransactionRouter ignores atClusterTime setting in the request

Closed

Assignee:: [DO NOT USE] Backlog - Cluster Scalability
Reporter:: Randolph Tan
Participants:: [DO NOT USE] Backlog - Cluster Scalability, Max Hirschhorn, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Aug 04 2023 08:07:25 PM UTC
Updated:: Nov 20 2023 09:05:22 PM UTC