The solution that SERVER-134701 opted for was to process each truncateRange oplog entry in its own batch. This can be quite slow.

On the other hand, processing too many in one batch can lead back to the issue described in SERVER-134701.

This ticket captures the work needed to dynamically size the number of entries processed in a single batch based on the size of the cache and the size of the work described by the oplog entry, etc.