Check for matching read concern in txn metadata when added participant continues txn

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2024-2-5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a shard receives a request with startOrContinueTransaction, resulting in the shard continuing the current transaction (it's already a participant), the shard checks that the request's txn metadata for read concern matches the txn's read concern.
      If there is no match, then...

            Assignee:
            Janna Golden (Inactive)
            Reporter:
            Israel Hsu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: