[SERVER-33633] Create jstestfuzz suite to enable the checkForInterruptFail failpoint Created: 02/Mar/18  Updated: 29/Oct/23  Resolved: 28/Mar/18

Status: Closed
Project: Core Server
Component/s: Storage, Testing Infrastructure
Affects Version/s: 3.7.3
Fix Version/s: 3.7.4

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-03-26, Storage NYC 2018-04-09
Participants:

 Description   

Since SERVER-32638, any lock acquisition can be interrupted when an OperationContext is killed. We should create a fuzzer suite that enables the checkForInterruptFail failpoint.

Two parameters will be passed to TestData:

  • enableCheckForInterruptFailpoint: boolean (asks the fuzzer to enable the failpoint on its connectionID )
  • checkForInterruptFailpointChance: double (sets the probability from 0 to 1 of activating the failpoint)

There are required changes in the fuzzer (TIG-758) to 1) disable the failpoint during the preamble and 2) re-enable it before the first statement runs.



 Comments   
Comment by Githook User [ 28/Mar/18 ]

Author:

{'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}

Message: SERVER-33633 Create jstestfuzz_interrupt and jstestfuzz_interrupt_replication suites to enable checkForInterrupt failpoint
Branch: master
https://github.com/mongodb/mongo/commit/e5a37389a86bcc366712df9a629724b1c97e09cd

Comment by Geert Bosch [ 23/Mar/18 ]

louis.williams, you should be unblocked now for SERVER-33633. Use something like this.

Generated at Thu Feb 08 04:34:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.