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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.10, 3.5.13
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2017-09-11
    • Linked BF Score:
      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

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-47695 Write commands run by threads that can survive rollback can fail operationTime invariant in ServiceEntryPoint

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              spencer Spencer Brody (Inactive)
              Reporter:
              spencer Spencer Brody (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: