SERVER-137175ClosedFixed

Change when fetchOplogFromORPAndApply resets attempts

Consider changing when we reset attempts counter in fetchOplogFromORPAndApply. Currently we do so on any progress, even progress that doesn't advance the LSN. Should we change it to a stricter LSN-advancing version? Also investigate the the difference between queued and applied oplog entries, and how we distinguish reset attempts (if entries got read from ORP and queued, but not applied, does this count as a failed attempt that we retry? That sets us back in our recovery progress as well.)

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

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

No components specified.

Labels
Tags and classification

No labels assigned.