- 
    Type:
Improvement
 - 
    Resolution: Unresolved
 - 
    Priority:
Major - P3
 - 
    None
 - 
    Affects Version/s: None
 - 
    Component/s: None
 - 
    None
 
- 
        Storage Engines, Storage Engines - Server Integration
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
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
- depends on
 - 
                    
SERVER-69615 Rollback fuzzing in WiredTiger leads to size storer marked dirty at shutdown
-         
 - Closed
 
 -         
 - 
                    
SERVER-69701 Timeseries multi document insert doesn't handle WiredTiger rollback correctly
-         
 - Closed
 
 -         
 - 
                    
SERVER-70343 Make time series tests resilient to WCEs
-         
 - Backlog
 
 -         
 - 
                    
SERVER-69699 dropRole transaction doesn't handle WiredTiger's rollback return
-         
 - Closed
 
 -         
 
- mentioned in
 - 
                    
Page Loading...