SERVER-138467ClosedFixed

Always describe oplog mayTruncateUpTo as an exclusive upper bound

Update code comments to make sure that oplog mayTruncateUpTo is always described as an exclusive upper bound. The oplog truncation contract is that at least one record with recordId <= mayTruncateUpTo must remain in the oplog after truncation. Also add a short-circuit to skip checking the persisted timestamp when all records are pinned.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.