-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Build
-
None
-
Storage Engines - Server Integration
-
SESIRuby4Prezident 2026-08-25
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The standby read path currently treats the resolver's answer not as final. If the read position resolves to a different segment than the connected one, the request is still sent to the connected segment which can lead to silently skipping a sealed segment's unapplied entries
Force reconnect on mismatch and add an upper bound. Also add a struct to track the ways in which we can reconnect (from our LSN known, stream from start etc). Supersedes _shouldReadFromSegmentStart
[Patch build here](https://spruce.corp.mongodb.com/version/6a79f32f6ee1c80007ce269c/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC)
10 green Chaos patch runs 🟢