[SERVER-21332] Add FSM runners that always enable the WTWriteConflictException failpoint Created: 06/Nov/15  Updated: 06/Dec/22  Resolved: 28/May/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.2.0-rc2
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kamran K. Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: stm, tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-40820 Jstestfuzz suite to introduce spuriou... Closed
Assigned Teams:
Storage Execution
Sprint: TIG C (11/20/15), TIG D (12/11/15)
Participants:

 Description   

We should add FSM runners that always enable the WTWriteConflictException failpoint for the cluster's lifetime.

Notes:
1 - The runner should skip tests if TestData.storageEngine is not an empty string or not 'wiredTiger'
2 - We need to figure out a reasonable probability to set in the failpoint
3 - SERVER-17103 might require us to blacklist certain workloads



 Comments   
Comment by Brooke Miller [ 28/May/20 ]

Assigning to Execution as STM doesn't have immediate plans to support this ticket. If you feel this is something you don't want, please feel free to close.

Generated at Thu Feb 08 03:57:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.