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

Don't try to set last optime for client backwards after rollback

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.4.10, 3.5.13
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-09-11
    • 0

    Description

      A write that fails may result in a call to setLastOpToSystemLastOpTime. We invariant that the last optime on a client never goes backwards, but the system optime can indeed go backwards after a rollback. If that happens we should just refuse to set the last optime on the client backwards, but we shouldn't crash.

      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: