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

computeAtClusterTimeForOneShard should always return the latest logical clock time

    XMLWordPrintable

    Details

      Description

      Currently when mongoS chooses an atClusterTime for queries it knows targets only one shard, it will choose the latest lastCommitted opTime timestamp it has seen from the shard. This will eventually be changed to use the latest lastApplied opTime timestamp to leverage speculative snapshot behavior, but until then, to enable testing of transactions on single shards with enableMajorityReadConcern=false, the computed time should instead always be the latest time in the router's logical clock. This matches the existing behavior for writes and for reads that target multiple shards.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: