-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Server Integration
-
SESIPreview 2026-10-20, SESIWhinery 2026-11-17, SESINickBeckenhome 2026-12-01
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the decision function says kFallbackToORP, we should set some fallback requested flag and return a normal connection failure error. The decision function site itself doesn't run the ORP, we need to bubble it back up so the run loop does the ORP read and the flag says that this wasn't a network problem.
For this ticket, we let the run loop see the flag and perform the fetch and reconnect. Fetch our missing range from ORP, apply it, then call the normal connect path to cut back to the LS. The next ticket will address our desired cutback mechanism.
Handle any interim failures in the run loop too by reopening the ORP stream from the last applied enqueued entry. If we keep failing, crash after bounded retries which will restart the recovery process.
- is depended on by
-
SERVER-135691 Cutback to LS mechanism wiring
-
- In Progress
-
- related to
-
SERVER-136803 Chain validation across ORP and LS entries
-
- Closed
-