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

We should fail operations with an atClusterTime readConcern newer than the current clusterTime

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.7.4
    • None
    • Replication, Sharding
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-03-26
    • 0

    Description

      Generally speaking atClusterTime readConcern is sent via mongos, which will also include $clusterTime metadata to advance the clock. If, however, an atClusterTime readConcern was received without $clusterTime metadata, or with a $clusterTime less than the atClusterTime value, then the no-op write performed by the read concern machinery might fail to advance the clock, and the read can block forever waiting for the cluster time to advance. Instead of hanging forever, the read should fail.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: