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

Add invariant that a transaction's read timestamp satisfies read concern constraints

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • Replication
    • v4.4, v4.2
    • 35

    Description

      If a startTransaction comes in with an afterClusterTime, we never validate that the readTimestamp captured here actually satisfied the afterClusterTime.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: