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

setAppliedThrough must set orderedCommit=false on the recovery unit

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • 20

    Description

      When we do a timestamped write that may not be strictly ordered with respect to the oplog (that is, if it has a timestamp less than or equal to the latest optime in the oplog), we must set orderedCommit to false to ensure oplog visibility is updated. ReplicationConsistencyMarkers::setAppliedThrough does not do this.

      It might make sense to do this in StorageInterfaceImpl::_updateWithQuery to catch any others.

      Attachments

        Activity

          People

            matthew.russotto@mongodb.com Matthew Russotto
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: