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

Test single shard transactions with arbiters and enableMajorityReadConcern:false replica sets with lag

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.7
    • Component/s: Replication
    • Labels:
      None

      Description

      Transactions that touch a single shard that contains an arbiter or contains a node with enableMajorityReadConcern:false will be allowed in 4.2. We should test that:

      1. A single shard transaction can succeed against a replica set that contains an arbiter.
      2. A single shard transaction can succeed against a replica set whose primary has enableMajorityReadConcern:false and whose secondary is lagged. We should test this to make sure that the transaction is selecting a read timestamp based on lastApplied, as opposed to starting at the majority commit point. If it started at the majority commit point, we would not be able to obtain a snapshot, since we won't keep history back that far.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vesselina.ratcheva Vesselina Ratcheva
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: