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

Don't allow read commands to change global read timestamp for sharded transactions

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Sharding 2018-12-17, Sharding 2018-12-31

    Description

      As a holdover from Global Point in Time reads, find, aggregate, and distinct are able to change the global read timestamp of a transaction during execution, to allow picking a time based off the shards that would be targeted. This logic has been disabled until SERVER-36312 is completed, but these commands may still set the time forward, under the assumption that doing so is safe because any operations that would cause data to move would also force a stale shard version error. There's really no benefit from allowing this behavior, and it could possibly lead to obscure bugs, so it should be disabled and re-enabled as part of SERVER-36312.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: