Add back holdStableTimestampAtSpecificTimestamp failpoint that was removed from runnable code path

XMLWordPrintableJSON

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

      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:
              Will Schultz
              Reporter:
              Will Schultz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: