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

Compute atClusterTime for sharded transactions using lastApplied opTime timestamps of targeted shards

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sharding

      The atClusterTime selection algorithm designed for the Global Point in Time reads project uses the last majority committed opTime timestamps from each targeted shard to select an atClusterTime timestamp. This is incompatible with the speculative snapshot optimization and can lead to problems on shards with enableMajorityReadConcern=false, so instead the algorithm should use the last applied opTime timestamps of the targeted shards.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: