Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38733

Change majority read concern transaction passthroughs to use local read concern

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.7
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2018-12-31, Sharding 2019-01-14

      Description

      To get coverage of read your own writes behavior for local operations on a single node without causal consistency without failovers, there should be transaction passthrough suites that use transactions with "local" read concern and commit with w:1 write concern in non-causally consistent sessions. Non transaction operations should also use these read and write concerns.

      This can be done by changing the existing concurrency_sharded_replication_majority_multi_stmt_txn(_with_balancer) suites to use "local" read concern instead of "majority." These suites already commit with w:1 write concern.

      The existing multi_shard_majority_multi_stmt_txn suite should also be changed to use "local" read concern and its commit write concern should be changed from w:majority to w:1.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              jack.mulrow Jack Mulrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: