The config fuzzer can set eviction_dirty_trigger as low as ~20MB or possibly even lower. If it then runs a test which inserts large documents, it is possible that one of these operations may generate more dirty data than we allow for. Currently, this manifests as the operation hanging indefinitely. After
SERVER-61909, this may instead manifest as the operation failing and an error being returned to the user. However, even the latter may make tests unhappy if they expect these operations to succeed. We may want to consider re-evaluating the minimum bounds for the eviction settings that the config fuzzer can generate.