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

Upgrade could trigger invariant in replication recovery

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2018-05-21

      Description

      We allow upgrades after unclean shutdown. After an unclean shutdown, it's possible we'd have a non-null appliedThrough and a null stableTimestamp in wiredTiger (so it wouldn't be boost::none). We should add an "|| stableTimestamp->isNull()" check to this invariant: https://github.com/mongodb/mongo/blob/d12afa4fdda9c6b113e7be3b4d67d757b07b50b5/src/mongo/db/repl/replication_recovery.cpp#L215-L219

        Attachments

          Activity

            People

            Assignee:
            judah.schvimer Judah Schvimer
            Reporter:
            judah.schvimer Judah Schvimer
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: