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

Integrate atClusterTime selection on mongos with RouterSession

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Sharding 2018-08-13, Sharding 2018-08-27

    Description

      Currently, atClusterTime is chosen in the find and aggregate paths and directly put into the readConcerns of the requests created by those commands. Instead, atClusterTime should be placed on the RouterSession during targeting and added to requests in TransactionParticipant::attachTxnFieldsIfNeeded. snapshot level readConcern should also be disallowed on mongos for commands not in a multi statement transaction.

      Mongos may try several different atClusterTime values until it finds one that all shards can provide a snapshot at. Mongos should remember the first value that was successful, so every subsequent statement that targets a new shard can use it.

      Attachments

        Activity

          People

            cheahuychou.mao@mongodb.com Cheahuychou Mao
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: