ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication, Replication - Oplog and Recovery
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Implement proposed changes from WRITING-40450 to prevent a replaced node from going back in time and affecting the majority commit point:

      • Server changes so that initial sync (LIS or FCBIS) is not considered completed until it is caught up to the primary’s view of max(lastCommitted, my lastWritten) (from the beginning of initial sync).
      • Server changes so that a node seeded with a snapshot (any node already in the replset) starts with a catchup phase (in STARTUP2 state) to get to the current primary’s view of max(lastCommitted, my lastWritten) (the first observed majority commit point as of restart).

      These changes should be behind a feature flag.

      Before implementing these changes we need to make sure they are safe, this will be done in SERVER-136912.

      This is a followup from WRITING-39616.

            Assignee:
            Indy Prentice
            Reporter:
            Pierre Turin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: