-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Server Integration
-
SESIWhinery 2026-11-17, SESINickBeckenhome 2026-12-01
-
None
-
None
-
None
-
None
-
None
-
None
-
None
A standby catching up from ORP at startup is by definition definitely more than 2 minutes behind so SecondaryLagWatchdog will crash it mid catchup and we end up in the same restart loop
Either we should exempt the watchdog from running during ORP catchup or we should increase its limit during this time until we cutback to LS. I'm not sure how easy it is to pick a reasonable limit to increase to, so I'd think the less risky option here is to exempt.
Should also check oplogCatchUpForStepUpTimeoutMillis and standbyCrashAfterStaleSegmentRetriesMillis for the same problem since a cold start that steps up will go through ORP catchup first