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

Add back holdStableTimestampAtSpecificTimestamp failpoint that was removed from runnable code path

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2020-07-27

      In SERVER-47844, we removed the usage of _chooseStableOpTimeFromCandidates, which contains the holdStableTimestampAtSpecificTimestamp failpoint. No tests that use the failpoint are currently failing yet, but we should add this failpoint back to ensure correct test behavior.

            Assignee:
            william.schultz@mongodb.com William Schultz
            Reporter:
            william.schultz@mongodb.com William Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: