[SERVER-60415] No longer accept FailPointSetFailed errors on jstests that use migrationRecipientFailPostCommitRefresh failpoint Created: 04/Oct/21  Updated: 29/Oct/23  Resolved: 05/Jul/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-58991 Acquire the critical section on the r... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-07-11
Participants:

 Description   

SERVER-58991 introduces a new failpoint migrationRecipientFailPostCommitRefresh with semantics analogous to doNotRefreshRecipientAfterCommit. Because this new failpoint does not exist in 5.0 binaries, tests that are run on multiversion suites need to account for it's possible non-existence.

This ticket is to remove this relaxation after 6.0 has been released. At this point, multiversion tests will always run on binaries that support the new failpoint.



 Comments   
Comment by Githook User [ 05/Jul/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-60415 No longer accept FailPointSetFailed errors on jstests that use migrationRecipientFailPostCommitRefresh failpoint
Branch: master
https://github.com/mongodb/mongo/commit/a363278ae80ab6849ca1eb5b73c9b8555b8e64b8

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