SERVER-34938ClosedFixed

Secondary slowdown or hang due to content pinned in cache by single oplog batch

We only advance the oldest timestamp at oplog batch boundaries. This means that all dirty content generated by the application of the operations in a single batch will be pinned in cache. If the batch is large enough and the operations are heavy enough this dirty content can exceed eviction_dirty_trigger (default 20% of cache) and the rate of applying operations will become dramatically slower because it has to wait for the dirty data to be reduced below the threshold. This can be triggered b

Affected Versions
Versions known to exhibit this issue
3.6.33.6.4
Fixed Versions
Versions that include the fix
5.0.0-rc04.2.164.0.274.4.9
Components
Server components related to this issue
Replication
Labels
Tags and classification
dmd-perfformer-quick-wins