The mechanism for reducing history (enableMajorityReads=false) was forward ported from 3.6. In 3.6, MongoDB didn't fully timestamp all writes and thus relied on logging all table writes and performing rollback via refetch.

The forward port to 4.0 and master also ported the functionality of enabling logging of all tables. This impacts the goal of filesystem backups to be able to 1) copy majority committed data and 2) the ability to control, via replication recovery, playing data to a specific time T in the oplog.

This ticket is a placeholder to make sure we understand the limitations this introduces and discuss, with the backup team/product, what we can do as a whole to reduce the limitations for the least amount of effort.