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

Make sure the snapshot read timestamp is not older than the oldest available timestamp in prepare_conflict_read_concern_behavior.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-09-24
    • 12

      Sometimes it can become older than the oldest available timestamp and cause a SnapshotTooOld error

            Assignee:
            samy.lanka@mongodb.com Samyukta Lanka
            Reporter:
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: