[SERVER-49472] Add back holdStableTimestampAtSpecificTimestamp failpoint that was removed from runnable code path Created: 13/Jul/20  Updated: 29/Oct/23  Resolved: 13/Jul/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-47844 Update _setStableTimestampForStorage ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-07-27
Participants:

 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.



 Comments   
Comment by Githook User [ 13/Jul/20 ]

Author:

{'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}

Message: SERVER-49472 Add 'holdStableTimestampAtSpecificTimestamp' failpoint back to runnable code path
Branch: master
https://github.com/mongodb/mongo/commit/09d1ea41fb25867e7cb2510b06933c3aa6757306

Generated at Thu Feb 08 05:19:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.