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

Subsequent statements in a transaction should target shards using the global read timestamp

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05

      Description

      Currently, the multi-versioned routing table is only used when selecting a global read timestamp, to verify that the set of shards used to compute the read timestamp matches the set that would be targeted at that timestamp. Now that mongos supports multi statement transactions, subsequent statements should route their requests using the multi-versioned routing table corresponding to the already selected read timestamp.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: