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

Add back holdStableTimestampAtSpecificTimestamp failpoint that was removed from runnable code path

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2020-07-27

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              william.schultz William Schultz (Inactive)
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: