-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Server Integration
-
Fully Compatible
-
SESIroflcopter 2026-11-03
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.)
- related to
-
SERVER-139428 Make LSN progress check stricter to avoid unbounded retries
-
- Open
-