[SERVER-69697] Enable rollback_error config fuzz Created: 14/Sep/22  Updated: 08/May/23

Status: Blocked
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Sulabh Mahajan Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: louis-preferred
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-69615 Rollback fuzzing in WiredTiger leads ... Closed
depends on SERVER-69701 Timeseries multi document insert does... Closed
depends on SERVER-70343 Make time series tests resilient to WCEs Open
depends on SERVER-69699 dropRole transaction doesn't handle W... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

SERVER-66770 added some WiredTiger configurations to the config fuzzer. One of them is debug_mode=(rollback_error=N). This option forces WiredTiger to return rollback for every Nth operation. At the moment it triggers several bugs so I disabled it while checking in the change.

Re-enable the option once all dependant bugs are resolved.

Here is the relevant code in mongod_fuzzer_configs.py:

    # Rollback every Nth transaction. The values have been tuned after looking at how many
    # WiredTiger transactions happen per second for the config-fuzzed jstests.
    # The setting is trigerring bugs, disabled until they get resolved.
    # dbg_rollback_error = rng.choice([0, rng.randint(250, 1500)])
    dbg_rollback_error = 0


Generated at Thu Feb 08 06:14:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.